Apache-Reload
view release on metacpan or search on metacpan
- change -dev to -rc\d+ starting with -rc1
b. commit Changes
% svn ci -m "0.14 rc1" Changes
c. nuke any preinstalled Apache-Reload 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-Reload 0.14 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.14 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-Reload 0.14
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 and lib/Apache2/Reload.pm also
b. edit ./Changes:
- start a new item with incremented version + '-dev'
=item 0.15-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
(undo the change to the PAUSE menu item number in item 0d. above)
d. commit Changes
% svn ci -m "start 0.14-dev cycle" Changes RELEASE \
lib/Apache/Reload.pm lib/Apache2/Reload.pm
( run in 0.874 second using v1.01-cache-2.11-cpan-b16cb0d3907 )