perl-modperl-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From steve...@apache.org
Subject svn commit: r1759462 - /perl/Apache-SizeLimit/trunk/RELEASE
Date Tue, 06 Sep 2016 17:20:27 GMT
Author: stevehay
Date: Tue Sep  6 17:20:27 2016
New Revision: 1759462

URL: http://svn.apache.org/viewvc?rev=1759462&view=rev
Log:
Update RELEASE as per r1759430

Modified:
    perl/Apache-SizeLimit/trunk/RELEASE

Modified: perl/Apache-SizeLimit/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-SizeLimit/trunk/RELEASE?rev=1759462&r1=1759461&r2=1759462&view=diff
==============================================================================
--- perl/Apache-SizeLimit/trunk/RELEASE (original)
+++ perl/Apache-SizeLimit/trunk/RELEASE Tue Sep  6 17:20:27 2016
@@ -1,36 +1,36 @@
 Instructions for Apache-SizeLimit 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.
 
-    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
+   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
+   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
+   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.
+   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.
@@ -38,8 +38,7 @@ TODO:
      and Apache2::SizeLimit
 
 3/4. Configure 
-
-     MAINTAINER_BUILDING_RELEASE=1 perl Makefile.PL
+   % 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
@@ -51,31 +50,33 @@ TODO:
 
      - don't commit these (see dev@ archives)
 
-  b. nuke any preinstalled Apache-SizeLimit libs and run 'make test'
+  b. commit Changes
+     % svn ci -m "0.97 rc1" Changes
 
-  c. test that you can 'make install' and then run 'make test' again
+  c. nuke any preinstalled Apache-SizeLimit 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-SizeLimit 0.97 RC\d+
-
    (or maybe longer to give most people a chance to catch up). no need
    to tag this package
 
+   Subject: [RELEASE CANDIDATE] Apache-SizeLimit 0.97 RC\d+
+
   a. if problems are detected during stage 2, repeat stages 1 and 2.
 
-  $ md5 Apache-SizeLimit-0.97-rc1.tar.gz > Apache-SizeLimit-0.97-rc1.tar.gz.md5
-  $ sha256 Apache-SizeLimit-0.97-rc1.tar.gz > Apache-SizeLimit-0.97-rc1.tar.gz.sha256
-  $ gpg --detach-sign --armor Apache-SizeLimit-0.97-rc1.tar.gz
+   % md5 Apache-SizeLimit-0.97-rc1.tar.gz > Apache-SizeLimit-0.97-rc1.tar.gz.md5
+   % sha256 Apache-SizeLimit-0.97-rc1.tar.gz > Apache-SizeLimit-0.97-rc1.tar.gz.sha256
+   % gpg --detach-sign --armor Apache-SizeLimit-0.97-rc1.tar.gz
 
 3. when the package has been reported to be good, prepare a new
    package to be released
@@ -90,7 +91,7 @@ TODO:
      % make -n tag
 
   c. commit Changes and modules
-     % svn ci Changes lib/
+     % svn ci -m "0.97 release" Changes lib/
 
   d. tag
      % make tag
@@ -104,11 +105,16 @@ TODO:
 
 5. Announce the package
 
-  a. post ... to the modperl, announce lists
-  Subject: [ANNOUNCE] Apache-SizeLimit 0.97
-     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-SizeLimit 0.97
+
+     include:
+     - MD5 sig (as it comes from CPAN upload announce).
+     - the latest Changes
 
 6. Prepare for the next cycle
 
@@ -117,12 +123,11 @@ TODO:
   b. edit ./Changes:
      - start a new item with incremented version + '-dev'
 
-  =item 0.98-dev
+     =item 0.98-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
 
   d. commit Changes
      % svn ci -m "start 0.98-dev cycle" Changes RELEASE lib/Apache/SizeLimit.pm lib/Apache2/SizeLimit.pm
lib/Apache/SizeLimit/Core.pm



Mime
View raw message