Author: stevehay Date: Tue Sep 6 17:19:37 2016 New Revision: 1759461 URL: http://svn.apache.org/viewvc?rev=1759461&view=rev Log: Update RELEASE as per r1759430
Modified: perl/Apache-Reload/trunk/RELEASE Modified: perl/Apache-Reload/trunk/RELEASE URL: http://svn.apache.org/viewvc/perl/Apache-Reload/trunk/RELEASE?rev=1759461&r1=1759460&r2=1759461&view=diff ============================================================================== --- perl/Apache-Reload/trunk/RELEASE (original) +++ perl/Apache-Reload/trunk/RELEASE Tue Sep 6 17:19:37 2016 @@ -1,22 +1,21 @@ Instructions for Apache-Reload Release Manager -0. Ask the PMC to verify that you have the appropriate CPAN permissions - on dev@perl. +0. Ask the PMC to verify that you have the appropriate CPAN permissions + on dev@perl. - 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 Change Permissions 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. - - MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL + 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 Change Permissions 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. + % 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) @@ -26,26 +25,28 @@ Instructions for Apache-Reload Release M a. edit ./Changes: - change -dev to -rc\d+ starting with -rc1 - b. nuke any preinstalled Apache-Reload libs and run 'make test' + b. commit Changes + % svn ci -m "0.14 rc1" Changes - c. test that you can 'make install' and then run 'make test' again + c. nuke any preinstalled Apache-Reload libs and run 'make test' - d. test whether we still 100% OK on systems with no LWP: + 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, upload a release candidate - to people.apache.org/~username and post 24 hour-ish candidate alert - to the various lists +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 - Subject: [RELEASE CANDIDATE] Apache-Reload 0.14 RC\d+ - (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 @@ -61,7 +62,7 @@ Instructions for Apache-Reload Release M % make -n tag c. commit Changes - % svn ci Changes + % svn ci -m "0.14 release" Changes d. tag % make tag @@ -75,11 +76,16 @@ Instructions for Apache-Reload Release M 5. Announce the package - a. post ... to the modperl, announce lists - Subject: [ANNOUNCE] Apache-Reload 0.14 - include - - MD5 sig (as it comes from CPAN upload announce). - - the latest Changes + a. post to the following lists: + + o modperl/perl.apache.org + o announce/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 @@ -88,12 +94,11 @@ Instructions for Apache-Reload Release M b. edit ./Changes: - start a new item with incremented version + '-dev' - =item 0.15-dev + =item 0.15-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 + % 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)