Author: stevehay
Date: Wed Apr 22 07:41:03 2015
New Revision: 1675267
URL: http://svn.apache.org/r1675267
Log:
start 0.13-dev cycle
[.This should have been done when 0.12 was made, but seems to have been forgotten. Doing it now since we're about to start the release process for 0.13.]
Modified:
perl/Apache-Reload/trunk/Changes
perl/Apache-Reload/trunk/RELEASE
perl/Apache-Reload/trunk/lib/Apache/Reload.pm
Modified: perl/Apache-Reload/trunk/Changes
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/Changes?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/Changes (original)
+++ perl/Apache-Reload/trunk/Changes Wed Apr 22 07:41:03 2015
@@ -6,6 +6,8 @@ Changes - Apache::Reload change logfile
=over 1
+=item 0.13-dev
+
=item 0.12 March 31, 2012
Set the -apxs argument correctly when building from mod_perl.
Modified: perl/Apache-Reload/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/RELEASE?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/RELEASE (original)
+++ perl/Apache-Reload/trunk/RELEASE Wed Apr 22 07:41:03 2015
@@ -1,120 +1,120 @@
-Instructions for Apache-Reload Release Manager
-
-0. Ask the PMC to verify that you have the appropriate CPAN permissions
- on dev@perl.
-
- make sure your public key is in the KEYS file in the mod_perl docs.
- you should only need to do this if this is your first time playing
- Release Manager
-
- $ cd mod_perl-docs
- $ grep $USER src/dist/KEYS
-
- note that the KEYS file itself contains all the instructions you
- need on how to add your key. if you need further help on gpg
- (like how to create a key in the first place) you can look here
-
- http://people.apache.org/~geoff/gpghowto.html
-
- Copy the KEYS file into place:
- % scp KEYS www.apache.org:/www/www.apache.org/dist/perl/KEYS
-
- If this is your first release, ask someone with APML karma on PAUSE
- to verify you have the appropriate permissions. Likely someone on
- the PMC can do this.
-
- a. login into https://pause.perl.org
- b. menu click: Select Mailinglist/Action
- c. choose APML and share_perms and click go
- d. click 3.3 Make somebody else co-maintainer
- e. choose the modules to give the perms to
- type the username of the new co-maintainer
- f. if you happen to know that packages were added this release,
- make sure you give the correct permissions to them.
-
- MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
-
-1. 'make disttest' - to make sure nothing is missing from the manifest.
- Now 'make dist', and test this generated package (not svn)
- with as many configurations as possible on as many platforms
- as possible.
-
- a. edit ./Changes:
- - find lib -type f -name "*.pm" | \
- xargs perl -pi -e 's,0.12-dev,0.12-rc1,g'
- - perl -pi -e 's,0.12-dev,0.12-rc1,g' Changes
-
- - don't commit these (see dev@ archives)
-
- b. nuke any preinstalled Apache-Reload libs and run 'make test'
-
- c. test that you can 'make install' and then run 'make test' again
-
- d. test whether we still 100% OK on systems with no LWP:
-
- % APACHE_TEST_PRETEND_NO_LWP=1 make test
-
-2. once confident that the package is good, upload a release candidate
- to people.apache.org/~username and post 24 hour-ish candidate alert
- to the various lists
-
- o dev/perl.apache.org
- o modperl/perl.apache.org
-
- Subject: [RELEASE CANDIDATE] Apache-Reload 0.12 RC\d+
-
- (or maybe longer to give most people a chance to catch up). no need
- to tag this package
-
- a. if problems are detected during stage 2, repeat stages 1 and 2.
-
-3. when the package has been reported to be good, prepare a new
- package to be released
-
- a. edit ./Changes
- - remove -rc\d+ (from lib/Apache/Reload.pm and lib/Apache2/Reload.pm also)
- - add release date
-
- b. rerun:
- % perl Makefile.PL
- make sure tag looks right
- % make -n tag
-
- c. commit Changes
- % svn ci Changes
-
- d. tag
- % make tag
-
- e. create the final package
- % make dist
-
- f. test the final package again at least once
-
-4. Upload the package to CPAN
-
-5. Announce the package
-
- a. post ... to the modperl, announce lists
- Subject: [ANNOUNCE] Apache-Reload 0.12
- include
- - MD5 sig (as it comes from CPAN upload announce).
- - the latest Changes
-
-6. Prepare for the next cycle
-
- a. increment version in lib/Apache/Reload.pm
-
- b. edit ./Changes:
- - start a new item with incremented version + '-dev'
-
- =item 0.13-dev
-
- c. bump up version numbers in this file to make it easier to do the
- next release.
-
- $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
-
- d. commit Changes
- % svn ci -m "start 0.12-dev cycle" Changes RELEASE \
- lib/Apache/Reload.pm lib/Apache2/Reload.pm
+Instructions for Apache-Reload Release Manager
+
+0. Ask the PMC to verify that you have the appropriate CPAN permissions
+ on dev@perl.
+
+ make sure your public key is in the KEYS file in the mod_perl docs.
+ you should only need to do this if this is your first time playing
+ Release Manager
+
+ $ cd mod_perl-docs
+ $ grep $USER src/dist/KEYS
+
+ note that the KEYS file itself contains all the instructions you
+ need on how to add your key. if you need further help on gpg
+ (like how to create a key in the first place) you can look here
+
+ http://people.apache.org/~geoff/gpghowto.html
+
+ Copy the KEYS file into place:
+ % scp KEYS www.apache.org:/www/www.apache.org/dist/perl/KEYS
+
+ If this is your first release, ask someone with APML karma on PAUSE
+ to verify you have the appropriate permissions. Likely someone on
+ the PMC can do this.
+
+ a. login into https://pause.perl.org
+ b. menu click: Select Mailinglist/Action
+ c. choose APML and share_perms and click go
+ d. click 3.3 Make somebody else co-maintainer
+ e. choose the modules to give the perms to
+ type the username of the new co-maintainer
+ f. if you happen to know that packages were added this release,
+ make sure you give the correct permissions to them.
+
+ MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
+
+1. 'make disttest' - to make sure nothing is missing from the manifest.
+ Now 'make dist', and test this generated package (not svn)
+ with as many configurations as possible on as many platforms
+ as possible.
+
+ a. edit ./Changes:
+ - find lib -type f -name "*.pm" | \
+ xargs perl -pi -e 's,0.13-dev,0.13-rc1,g'
+ - perl -pi -e 's,0.13-dev,0.13-rc1,g' Changes
+
+ - don't commit these (see dev@ archives)
+
+ b. nuke any preinstalled Apache-Reload libs and run 'make test'
+
+ c. test that you can 'make install' and then run 'make test' again
+
+ d. test whether we still 100% OK on systems with no LWP:
+
+ % APACHE_TEST_PRETEND_NO_LWP=1 make test
+
+2. once confident that the package is good, upload a release candidate
+ to people.apache.org/~username and post 24 hour-ish candidate alert
+ to the various lists
+
+ o dev/perl.apache.org
+ o modperl/perl.apache.org
+
+ Subject: [RELEASE CANDIDATE] Apache-Reload 0.13 RC\d+
+
+ (or maybe longer to give most people a chance to catch up). no need
+ to tag this package
+
+ a. if problems are detected during stage 2, repeat stages 1 and 2.
+
+3. when the package has been reported to be good, prepare a new
+ package to be released
+
+ a. edit ./Changes
+ - remove -rc\d+ (from lib/Apache/Reload.pm and lib/Apache2/Reload.pm also)
+ - add release date
+
+ b. rerun:
+ % perl Makefile.PL
+ make sure tag looks right
+ % make -n tag
+
+ c. commit Changes
+ % svn ci Changes
+
+ d. tag
+ % make tag
+
+ e. create the final package
+ % make dist
+
+ f. test the final package again at least once
+
+4. Upload the package to CPAN
+
+5. Announce the package
+
+ a. post ... to the modperl, announce lists
+ Subject: [ANNOUNCE] Apache-Reload 0.13
+ include
+ - MD5 sig (as it comes from CPAN upload announce).
+ - the latest Changes
+
+6. Prepare for the next cycle
+
+ a. increment version in lib/Apache/Reload.pm
+
+ b. edit ./Changes:
+ - start a new item with incremented version + '-dev'
+
+ =item 0.14-dev
+
+ c. bump up version numbers in this file to make it easier to do the
+ next release.
+
+ $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
+
+ d. commit Changes
+ % svn ci -m "start 0.13-dev cycle" Changes RELEASE \
+ lib/Apache/Reload.pm lib/Apache2/Reload.pm
Modified: perl/Apache-Reload/trunk/lib/Apache/Reload.pm
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/lib/Apache/Reload.pm?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/lib/Apache/Reload.pm (original)
+++ perl/Apache-Reload/trunk/lib/Apache/Reload.pm Wed Apr 22 07:41:03 2015
@@ -17,7 +17,7 @@ package Apache::Reload;
use strict;
-$Apache::Reload::VERSION = '0.12';
+$Apache::Reload::VERSION = '0.13';
use vars qw(%INCS %Stat $TouchTime %UndefFields %Ignore);
Date: Wed Apr 22 07:41:03 2015
New Revision: 1675267
URL: http://svn.apache.org/r1675267
Log:
start 0.13-dev cycle
[.This should have been done when 0.12 was made, but seems to have been forgotten. Doing it now since we're about to start the release process for 0.13.]
Modified:
perl/Apache-Reload/trunk/Changes
perl/Apache-Reload/trunk/RELEASE
perl/Apache-Reload/trunk/lib/Apache/Reload.pm
Modified: perl/Apache-Reload/trunk/Changes
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/Changes?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/Changes (original)
+++ perl/Apache-Reload/trunk/Changes Wed Apr 22 07:41:03 2015
@@ -6,6 +6,8 @@ Changes - Apache::Reload change logfile
=over 1
+=item 0.13-dev
+
=item 0.12 March 31, 2012
Set the -apxs argument correctly when building from mod_perl.
Modified: perl/Apache-Reload/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/RELEASE?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/RELEASE (original)
+++ perl/Apache-Reload/trunk/RELEASE Wed Apr 22 07:41:03 2015
@@ -1,120 +1,120 @@
-Instructions for Apache-Reload Release Manager
-
-0. Ask the PMC to verify that you have the appropriate CPAN permissions
- on dev@perl.
-
- make sure your public key is in the KEYS file in the mod_perl docs.
- you should only need to do this if this is your first time playing
- Release Manager
-
- $ cd mod_perl-docs
- $ grep $USER src/dist/KEYS
-
- note that the KEYS file itself contains all the instructions you
- need on how to add your key. if you need further help on gpg
- (like how to create a key in the first place) you can look here
-
- http://people.apache.org/~geoff/gpghowto.html
-
- Copy the KEYS file into place:
- % scp KEYS www.apache.org:/www/www.apache.org/dist/perl/KEYS
-
- If this is your first release, ask someone with APML karma on PAUSE
- to verify you have the appropriate permissions. Likely someone on
- the PMC can do this.
-
- a. login into https://pause.perl.org
- b. menu click: Select Mailinglist/Action
- c. choose APML and share_perms and click go
- d. click 3.3 Make somebody else co-maintainer
- e. choose the modules to give the perms to
- type the username of the new co-maintainer
- f. if you happen to know that packages were added this release,
- make sure you give the correct permissions to them.
-
- MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
-
-1. 'make disttest' - to make sure nothing is missing from the manifest.
- Now 'make dist', and test this generated package (not svn)
- with as many configurations as possible on as many platforms
- as possible.
-
- a. edit ./Changes:
- - find lib -type f -name "*.pm" | \
- xargs perl -pi -e 's,0.12-dev,0.12-rc1,g'
- - perl -pi -e 's,0.12-dev,0.12-rc1,g' Changes
-
- - don't commit these (see dev@ archives)
-
- b. nuke any preinstalled Apache-Reload libs and run 'make test'
-
- c. test that you can 'make install' and then run 'make test' again
-
- d. test whether we still 100% OK on systems with no LWP:
-
- % APACHE_TEST_PRETEND_NO_LWP=1 make test
-
-2. once confident that the package is good, upload a release candidate
- to people.apache.org/~username and post 24 hour-ish candidate alert
- to the various lists
-
- o dev/perl.apache.org
- o modperl/perl.apache.org
-
- Subject: [RELEASE CANDIDATE] Apache-Reload 0.12 RC\d+
-
- (or maybe longer to give most people a chance to catch up). no need
- to tag this package
-
- a. if problems are detected during stage 2, repeat stages 1 and 2.
-
-3. when the package has been reported to be good, prepare a new
- package to be released
-
- a. edit ./Changes
- - remove -rc\d+ (from lib/Apache/Reload.pm and lib/Apache2/Reload.pm also)
- - add release date
-
- b. rerun:
- % perl Makefile.PL
- make sure tag looks right
- % make -n tag
-
- c. commit Changes
- % svn ci Changes
-
- d. tag
- % make tag
-
- e. create the final package
- % make dist
-
- f. test the final package again at least once
-
-4. Upload the package to CPAN
-
-5. Announce the package
-
- a. post ... to the modperl, announce lists
- Subject: [ANNOUNCE] Apache-Reload 0.12
- include
- - MD5 sig (as it comes from CPAN upload announce).
- - the latest Changes
-
-6. Prepare for the next cycle
-
- a. increment version in lib/Apache/Reload.pm
-
- b. edit ./Changes:
- - start a new item with incremented version + '-dev'
-
- =item 0.13-dev
-
- c. bump up version numbers in this file to make it easier to do the
- next release.
-
- $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
-
- d. commit Changes
- % svn ci -m "start 0.12-dev cycle" Changes RELEASE \
- lib/Apache/Reload.pm lib/Apache2/Reload.pm
+Instructions for Apache-Reload Release Manager
+
+0. Ask the PMC to verify that you have the appropriate CPAN permissions
+ on dev@perl.
+
+ make sure your public key is in the KEYS file in the mod_perl docs.
+ you should only need to do this if this is your first time playing
+ Release Manager
+
+ $ cd mod_perl-docs
+ $ grep $USER src/dist/KEYS
+
+ note that the KEYS file itself contains all the instructions you
+ need on how to add your key. if you need further help on gpg
+ (like how to create a key in the first place) you can look here
+
+ http://people.apache.org/~geoff/gpghowto.html
+
+ Copy the KEYS file into place:
+ % scp KEYS www.apache.org:/www/www.apache.org/dist/perl/KEYS
+
+ If this is your first release, ask someone with APML karma on PAUSE
+ to verify you have the appropriate permissions. Likely someone on
+ the PMC can do this.
+
+ a. login into https://pause.perl.org
+ b. menu click: Select Mailinglist/Action
+ c. choose APML and share_perms and click go
+ d. click 3.3 Make somebody else co-maintainer
+ e. choose the modules to give the perms to
+ type the username of the new co-maintainer
+ f. if you happen to know that packages were added this release,
+ make sure you give the correct permissions to them.
+
+ MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
+
+1. 'make disttest' - to make sure nothing is missing from the manifest.
+ Now 'make dist', and test this generated package (not svn)
+ with as many configurations as possible on as many platforms
+ as possible.
+
+ a. edit ./Changes:
+ - find lib -type f -name "*.pm" | \
+ xargs perl -pi -e 's,0.13-dev,0.13-rc1,g'
+ - perl -pi -e 's,0.13-dev,0.13-rc1,g' Changes
+
+ - don't commit these (see dev@ archives)
+
+ b. nuke any preinstalled Apache-Reload libs and run 'make test'
+
+ c. test that you can 'make install' and then run 'make test' again
+
+ d. test whether we still 100% OK on systems with no LWP:
+
+ % APACHE_TEST_PRETEND_NO_LWP=1 make test
+
+2. once confident that the package is good, upload a release candidate
+ to people.apache.org/~username and post 24 hour-ish candidate alert
+ to the various lists
+
+ o dev/perl.apache.org
+ o modperl/perl.apache.org
+
+ Subject: [RELEASE CANDIDATE] Apache-Reload 0.13 RC\d+
+
+ (or maybe longer to give most people a chance to catch up). no need
+ to tag this package
+
+ a. if problems are detected during stage 2, repeat stages 1 and 2.
+
+3. when the package has been reported to be good, prepare a new
+ package to be released
+
+ a. edit ./Changes
+ - remove -rc\d+ (from lib/Apache/Reload.pm and lib/Apache2/Reload.pm also)
+ - add release date
+
+ b. rerun:
+ % perl Makefile.PL
+ make sure tag looks right
+ % make -n tag
+
+ c. commit Changes
+ % svn ci Changes
+
+ d. tag
+ % make tag
+
+ e. create the final package
+ % make dist
+
+ f. test the final package again at least once
+
+4. Upload the package to CPAN
+
+5. Announce the package
+
+ a. post ... to the modperl, announce lists
+ Subject: [ANNOUNCE] Apache-Reload 0.13
+ include
+ - MD5 sig (as it comes from CPAN upload announce).
+ - the latest Changes
+
+6. Prepare for the next cycle
+
+ a. increment version in lib/Apache/Reload.pm
+
+ b. edit ./Changes:
+ - start a new item with incremented version + '-dev'
+
+ =item 0.14-dev
+
+ c. bump up version numbers in this file to make it easier to do the
+ next release.
+
+ $ perl -pi -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
+
+ d. commit Changes
+ % svn ci -m "start 0.13-dev cycle" Changes RELEASE \
+ lib/Apache/Reload.pm lib/Apache2/Reload.pm
Modified: perl/Apache-Reload/trunk/lib/Apache/Reload.pm
URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/lib/Apache/Reload.pm?rev=1675267&r1=1675266&r2=1675267&view=diff
==============================================================================
--- perl/Apache-Reload/trunk/lib/Apache/Reload.pm (original)
+++ perl/Apache-Reload/trunk/lib/Apache/Reload.pm Wed Apr 22 07:41:03 2015
@@ -17,7 +17,7 @@ package Apache::Reload;
use strict;
-$Apache::Reload::VERSION = '0.12';
+$Apache::Reload::VERSION = '0.13';
use vars qw(%INCS %Stat $TouchTime %UndefFields %Ignore);