Author: stevehay
Date: Sun Aug 6 11:11:55 2023
New Revision: 1911486
URL: http://svn.apache.org/viewvc?rev=1911486&view=rev
Log:
start 0.99-dev cycle
Modified:
perl/Apache-SizeLimit/trunk/Changes
perl/Apache-SizeLimit/trunk/RELEASE
perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm
perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm
perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm
Modified: perl/Apache-SizeLimit/trunk/Changes
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/Changes?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/Changes (original)
+++ perl/Apache-SizeLimit/trunk/Changes Sun Aug 6 11:11:55 2023
@@ -6,6 +6,8 @@ Changes - Apache::SizeLimit change logfi
=over 6
+=item 0.99-dev
+
=item 0.98 August 06, 2023
Overhaul $VERSION numbering scheme to align with other mod_perl modules and
Modified: perl/Apache-SizeLimit/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/RELEASE?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/RELEASE (original)
+++ perl/Apache-SizeLimit/trunk/RELEASE Sun Aug 6 11:11:55 2023
@@ -1,125 +1,125 @@
-Instructions for Apache-SizeLimit 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.6 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.
-
-TODO:
-1/2. run pod2text to update the README and commit any changes if neccessary.
- Decide what to do about having almost identical pod in Apache::SizeLimit
- and Apache2::SizeLimit
-
-3/4. Configure
- % MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
-
-1. 'make dist' - to make sure nothing is missing from the manifest,
- etc. Now test this generated package (not svn) with as many
- configurations as possible on as many platforms as possible.
-
- a. edit ./Changes:
- - change -dev to -rc\d+ starting with -rc1
-
- b. commit Changes
- % svn ci -m "0.98 rc1" Changes
-
- c. nuke any preinstalled Apache-SizeLimit libs and run 'make test'
-
- d. test that you can 'make install' and then run 'make test' again
-
- e. test whether we are still 100% OK on systems with no LWP:
- % APACHE_TEST_PRETEND_NO_LWP=1 make test
-
-2. once confident that the package is good, commit the release candidate
- to https://dist.apache.org/repos/dist/dev/perl and post 24 hour-ish
- candidate alert to the various lists
-
- o dev/perl.apache.org
- o modperl/perl.apache.org
-
- (or maybe longer to give most people a chance to catch up). no need
- to tag this package
-
- Subject: [RELEASE CANDIDATE] Apache-SizeLimit 0.98 RC\d+
-
- 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+
- - add release date
-
- b. rerun:
- % perl Makefile.PL
- make sure tag looks right
- % make -n tag
-
- c. commit Changes
- % svn ci -m "0.98 release" 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 following list:
-
- o modperl/perl.apache.org
-
- Subject: [ANNOUNCE] Apache-SizeLimit 0.98
-
- 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/SizeLimit.pm, lib/Apache2/SizeLimit.pm and lib/Apache/SizeLimit/Core.pm
-
- b. edit ./Changes:
- - start a new item with incremented version + '-dev'
-
- =item 0.99-dev
-
- c. bump up version numbers in this file to make it easier to do the
- next release.
- % perl -pi.bak -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
-
- d. commit Changes
- % svn ci -m "start 0.99-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm lib/Apache2/SizeLimit.pm lib/Apache/SizeLimit/Core.pm
+Instructions for Apache-SizeLimit 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.1 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.
+
+TODO:
+1/2. run pod2text to update the README and commit any changes if neccessary.
+ Decide what to do about having almost identical pod in Apache::SizeLimit
+ and Apache2::SizeLimit
+
+3/4. Configure
+ % MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
+
+1. 'make dist' - to make sure nothing is missing from the manifest,
+ etc. Now test this generated package (not svn) with as many
+ configurations as possible on as many platforms as possible.
+
+ a. edit ./Changes:
+ - change -dev to -rc\d+ starting with -rc1
+
+ b. commit Changes
+ % svn ci -m "0.99 rc1" Changes
+
+ c. nuke any preinstalled Apache-SizeLimit libs and run 'make test'
+
+ d. test that you can 'make install' and then run 'make test' again
+
+ e. test whether we are still 100% OK on systems with no LWP:
+ % APACHE_TEST_PRETEND_NO_LWP=1 make test
+
+2. once confident that the package is good, commit the release candidate
+ to https://dist.apache.org/repos/dist/dev/perl and post 24 hour-ish
+ candidate alert to the various lists
+
+ o dev/perl.apache.org
+ o modperl/perl.apache.org
+
+ (or maybe longer to give most people a chance to catch up). no need
+ to tag this package
+
+ Subject: [RELEASE CANDIDATE] Apache-SizeLimit 0.99 RC\d+
+
+ 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+
+ - add release date
+
+ b. rerun:
+ % perl Makefile.PL
+ make sure tag looks right
+ % make -n tag
+
+ c. commit Changes
+ % svn ci -m "0.99 release" 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 following list:
+
+ o modperl/perl.apache.org
+
+ Subject: [ANNOUNCE] Apache-SizeLimit 0.99
+
+ 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/SizeLimit.pm, lib/Apache2/SizeLimit.pm and lib/Apache/SizeLimit/Core.pm
+
+ b. edit ./Changes:
+ - start a new item with incremented version + '-dev'
+
+ =item 1.00-dev
+
+ c. bump up version numbers in this file to make it easier to do the
+ next release.
+ % perl -pi.bak -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
+
+ d. commit Changes
+ % svn ci -m "start 0.99-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm lib/Apache2/SizeLimit.pm lib/Apache/SizeLimit/Core.pm
Modified: perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm Sun Aug 6 11:11:55 2023
@@ -26,7 +26,7 @@ use constant IS_WIN32 => $Config{'osname
use vars qw($VERSION);
-$VERSION = '0.98';
+$VERSION = '0.99';
use Apache::SizeLimit::Core qw(
$MAX_PROCESS_SIZE
Modified: perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm Sun Aug 6 11:11:55 2023
@@ -47,7 +47,7 @@ use vars qw(
$START_TIME
);
-$VERSION = '0.98';
+$VERSION = '0.99';
$REQUEST_COUNT = 1;
Modified: perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm Sun Aug 6 11:11:55 2023
@@ -34,7 +34,7 @@ die "Apache2::SizeLimit at the moment wo
use constant IS_WIN32 => $Config{'osname'} eq 'MSWin32' ? 1 : 0;
# 2.x requires 5.6.x+ so 'our' is okay
-our $VERSION = '0.98';
+our $VERSION = '0.99';
use Apache::SizeLimit::Core qw(
$MAX_PROCESS_SIZE
Date: Sun Aug 6 11:11:55 2023
New Revision: 1911486
URL: http://svn.apache.org/viewvc?rev=1911486&view=rev
Log:
start 0.99-dev cycle
Modified:
perl/Apache-SizeLimit/trunk/Changes
perl/Apache-SizeLimit/trunk/RELEASE
perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm
perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm
perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm
Modified: perl/Apache-SizeLimit/trunk/Changes
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/Changes?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/Changes (original)
+++ perl/Apache-SizeLimit/trunk/Changes Sun Aug 6 11:11:55 2023
@@ -6,6 +6,8 @@ Changes - Apache::SizeLimit change logfi
=over 6
+=item 0.99-dev
+
=item 0.98 August 06, 2023
Overhaul $VERSION numbering scheme to align with other mod_perl modules and
Modified: perl/Apache-SizeLimit/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/RELEASE?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/RELEASE (original)
+++ perl/Apache-SizeLimit/trunk/RELEASE Sun Aug 6 11:11:55 2023
@@ -1,125 +1,125 @@
-Instructions for Apache-SizeLimit 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.6 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.
-
-TODO:
-1/2. run pod2text to update the README and commit any changes if neccessary.
- Decide what to do about having almost identical pod in Apache::SizeLimit
- and Apache2::SizeLimit
-
-3/4. Configure
- % MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
-
-1. 'make dist' - to make sure nothing is missing from the manifest,
- etc. Now test this generated package (not svn) with as many
- configurations as possible on as many platforms as possible.
-
- a. edit ./Changes:
- - change -dev to -rc\d+ starting with -rc1
-
- b. commit Changes
- % svn ci -m "0.98 rc1" Changes
-
- c. nuke any preinstalled Apache-SizeLimit libs and run 'make test'
-
- d. test that you can 'make install' and then run 'make test' again
-
- e. test whether we are still 100% OK on systems with no LWP:
- % APACHE_TEST_PRETEND_NO_LWP=1 make test
-
-2. once confident that the package is good, commit the release candidate
- to https://dist.apache.org/repos/dist/dev/perl and post 24 hour-ish
- candidate alert to the various lists
-
- o dev/perl.apache.org
- o modperl/perl.apache.org
-
- (or maybe longer to give most people a chance to catch up). no need
- to tag this package
-
- Subject: [RELEASE CANDIDATE] Apache-SizeLimit 0.98 RC\d+
-
- 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+
- - add release date
-
- b. rerun:
- % perl Makefile.PL
- make sure tag looks right
- % make -n tag
-
- c. commit Changes
- % svn ci -m "0.98 release" 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 following list:
-
- o modperl/perl.apache.org
-
- Subject: [ANNOUNCE] Apache-SizeLimit 0.98
-
- 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/SizeLimit.pm, lib/Apache2/SizeLimit.pm and lib/Apache/SizeLimit/Core.pm
-
- b. edit ./Changes:
- - start a new item with incremented version + '-dev'
-
- =item 0.99-dev
-
- c. bump up version numbers in this file to make it easier to do the
- next release.
- % perl -pi.bak -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
-
- d. commit Changes
- % svn ci -m "start 0.99-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm lib/Apache2/SizeLimit.pm lib/Apache/SizeLimit/Core.pm
+Instructions for Apache-SizeLimit 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.1 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.
+
+TODO:
+1/2. run pod2text to update the README and commit any changes if neccessary.
+ Decide what to do about having almost identical pod in Apache::SizeLimit
+ and Apache2::SizeLimit
+
+3/4. Configure
+ % MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
+
+1. 'make dist' - to make sure nothing is missing from the manifest,
+ etc. Now test this generated package (not svn) with as many
+ configurations as possible on as many platforms as possible.
+
+ a. edit ./Changes:
+ - change -dev to -rc\d+ starting with -rc1
+
+ b. commit Changes
+ % svn ci -m "0.99 rc1" Changes
+
+ c. nuke any preinstalled Apache-SizeLimit libs and run 'make test'
+
+ d. test that you can 'make install' and then run 'make test' again
+
+ e. test whether we are still 100% OK on systems with no LWP:
+ % APACHE_TEST_PRETEND_NO_LWP=1 make test
+
+2. once confident that the package is good, commit the release candidate
+ to https://dist.apache.org/repos/dist/dev/perl and post 24 hour-ish
+ candidate alert to the various lists
+
+ o dev/perl.apache.org
+ o modperl/perl.apache.org
+
+ (or maybe longer to give most people a chance to catch up). no need
+ to tag this package
+
+ Subject: [RELEASE CANDIDATE] Apache-SizeLimit 0.99 RC\d+
+
+ 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+
+ - add release date
+
+ b. rerun:
+ % perl Makefile.PL
+ make sure tag looks right
+ % make -n tag
+
+ c. commit Changes
+ % svn ci -m "0.99 release" 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 following list:
+
+ o modperl/perl.apache.org
+
+ Subject: [ANNOUNCE] Apache-SizeLimit 0.99
+
+ 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/SizeLimit.pm, lib/Apache2/SizeLimit.pm and lib/Apache/SizeLimit/Core.pm
+
+ b. edit ./Changes:
+ - start a new item with incremented version + '-dev'
+
+ =item 1.00-dev
+
+ c. bump up version numbers in this file to make it easier to do the
+ next release.
+ % perl -pi.bak -e 's/(\d+)\.(\d+)/join(".", $1, $2+1)/eg' RELEASE
+
+ d. commit Changes
+ % svn ci -m "start 0.99-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm lib/Apache2/SizeLimit.pm lib/Apache/SizeLimit/Core.pm
Modified: perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit.pm Sun Aug 6 11:11:55 2023
@@ -26,7 +26,7 @@ use constant IS_WIN32 => $Config{'osname
use vars qw($VERSION);
-$VERSION = '0.98';
+$VERSION = '0.99';
use Apache::SizeLimit::Core qw(
$MAX_PROCESS_SIZE
Modified: perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache/SizeLimit/Core.pm Sun Aug 6 11:11:55 2023
@@ -47,7 +47,7 @@ use vars qw(
$START_TIME
);
-$VERSION = '0.98';
+$VERSION = '0.99';
$REQUEST_COUNT = 1;
Modified: perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm?rev=1911486&r1=1911485&r2=1911486&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm (original)
+++ perl/Apache-SizeLimit/trunk/lib/Apache2/SizeLimit.pm Sun Aug 6 11:11:55 2023
@@ -34,7 +34,7 @@ die "Apache2::SizeLimit at the moment wo
use constant IS_WIN32 => $Config{'osname'} eq 'MSWin32' ? 1 : 0;
# 2.x requires 5.6.x+ so 'our' is okay
-our $VERSION = '0.98';
+our $VERSION = '0.99';
use Apache::SizeLimit::Core qw(
$MAX_PROCESS_SIZE