perl-test-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From steve...@apache.org
Subject svn commit: r1759430 - /perl/Apache-Test/trunk/RELEASE
Date Tue, 06 Sep 2016 13:04:14 GMT
Author: stevehay
Date: Tue Sep  6 13:04:14 2016
New Revision: 1759430

URL: http://svn.apache.org/viewvc?rev=1759430&view=rev
Log:
Update RELEASE to reflect reality

The most important change here is that RCs should no longer be put in perl.apache.org/~username
- see:
https://reference.apache.org/committer/newaccount#personal-web-space

Modified:
    perl/Apache-Test/trunk/RELEASE

Modified: perl/Apache-Test/trunk/RELEASE
URL: http://svn.apache.org/viewvc/perl/Apache-Test/trunk/RELEASE?rev=1759430&r1=1759429&r2=1759430&view=diff
==============================================================================
--- perl/Apache-Test/trunk/RELEASE (original)
+++ perl/Apache-Test/trunk/RELEASE Tue Sep  6 13:04:14 2016
@@ -1,7 +1,7 @@
 Instructions for Apache-Test Release Manager
 
-0.  Ask the PMC to verify that you have the appropriate CPAN permissions
-    on test-dev@.
+0. Ask the PMC to verify that you have the appropriate CPAN permissions
+   on test-dev@.
 
 1. 'make dist' - to make sure nothing is missing from the manifest,
    etc. Now test this generated package (not svn) with as many
@@ -14,18 +14,20 @@ Instructions for Apache-Test Release Man
        this means that development proceeds with non '-dev' or '-rc1' version
        tags, so keep that in mind.
 
-  b. nuke any preinstalled Apache-Test libs and run 'make test'
+  b. commit Changes
+     % svn ci -m "1.41 rc1" Changes
 
-  c. test that you can 'make install' and then run 'make test' again
+  c. nuke any preinstalled Apache-Test 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 perl.apache.org/~username and post 24 hour-ish candidate alert
-   to the various lists.  note that you will need to be subscribed to
-   all of the following 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.  note that you will need to
+   be subscribed to all of the following lists.
 
      o test-dev/perl.apache.org
      o dev/perl.apache.org
@@ -52,7 +54,7 @@ Instructions for Apache-Test Release Man
      % make -n tag
 
   c. commit Changes
-     % svn ci Changes
+     % svn ci -m "1.41 release" Changes
 
   d. tag
      % make tag
@@ -66,11 +68,18 @@ Instructions for Apache-Test Release Man
 
 5. Announce the package
 
-  a. post ... to the modperl, announce lists
-  Subject: [ANNOUNCE] Apache-Test 1.41
-     include 
-  - MD5 sig (as it comes from CPAN upload announce).
-  - the latest Changes
+  a. post to the following lists:
+
+     o test-dev/perl.apache.org
+     o dev/perl.apache.org
+     o modperl/perl.apache.org
+     o announce/apache.org
+
+   Subject: [ANNOUNCE] Apache-Test-1.41
+
+     include:
+     - MD5 sig (as it comes from CPAN upload announce).
+     - the latest Changes
 
 6. Prepare for the next cycle
 
@@ -79,12 +88,11 @@ Instructions for Apache-Test Release Man
   b. edit ./Changes:
      - start a new item with incremented version + '-dev'
 
-  =item 1.42-dev
+     =item 1.42-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 1.41-dev cycle" Changes RELEASE lib/Apache/Test.pm



Mime
View raw message