Mailing-List: contact apreq-cvs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: apreq-dev@httpd.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r472780 - /httpd/apreq/branches/v2_09/build/RELEASE
Date: Thu, 09 Nov 2006 05:36:45 -0000
To: apreq-cvs@httpd.apache.org
From: pgollucci@apache.org
Message-Id: <20061109053645.A03D61A9846@eris.apache.org>

Author: pgollucci
Date: Wed Nov  8 21:36:43 2006
New Revision: 472780

URL: http://svn.apache.org/viewvc?view=rev&rev=472780
Log:
start signing the release candidates 

If the release candidate is going to become a release,
you know already have the .tar.gz and .asc file and need
to just scp them into place after voting

NO CHANGES!


Modified:
    httpd/apreq/branches/v2_09/build/RELEASE

Modified: httpd/apreq/branches/v2_09/build/RELEASE
URL: http://svn.apache.org/viewvc/httpd/apreq/branches/v2_09/build/RELEASE?view=diff&rev=472780&r1=472779&r2=472780
==============================================================================
--- httpd/apreq/branches/v2_09/build/RELEASE (original)
+++ httpd/apreq/branches/v2_09/build/RELEASE Wed Nov  8 21:36:43 2006
@@ -59,21 +59,28 @@
 
    Make sure all perl tests pass.
 
+6. Sign it via gpg:
 
-6. Upload the release candidate to people.apache.org/~username
+        % gpg --detach-sign --armor libapreq2-2.09.tar.gz
+
+   or pgp:
+
+        % pgp -sba libapreq2-2.09.tar.gz
+
+7. Upload the release candidate to people.apache.org/~username
    and post a candidate announcement to apreq-dev@. Also, it is 
    strongly recommended that the RM crosspost the candidate 
    announcement to the modperl@ list, to solicit feedback
    from a much larger audience.
 
 
-7. Give the mailing list participants 48-72 hours to comment and
+8. Give the mailing list participants 48-72 hours to comment and
    vote on the candidate.  If there is a "majority consensus" 
    (three +1 and more +1s than -1s) among the httpd pmc members, the RM 
    may proceed with the release.
 
 
-8. Tag the Release -- from the BRANCH
+9. Tag the Release -- from the BRANCH
 
     svn cp https://svn.apache.org/repos/asf/httpd/apreq/branches/v2_09 \
            https://svn.apache.org/repos/asf/httpd/apreq/tags/v2_09
@@ -81,19 +88,6 @@
     NOTE the Revision that is copied.  Call it $rE.
     It will be in the commit e-mail.
 
-9. Regenerate the release 
-
-        % make release && make release_test
-
-   Then test and sign it via gpg:
-
-        % gpg --detach-sign --armor libapreq2-2.09.tar.gz
-
-   or pgp:
-
-        % pgp -sba libapreq2-2.09.tar.gz
-
-
 10. Upload (scp) the package and signature to www.apache.org
    for distribution:
 
@@ -113,7 +107,7 @@
 
 11. Verify or get soeone to Verify that you have CPAN karma.
     Note, discuss getting a group kind of like AMPL in mod_perl land.
-    (Currently, joes@ is active and has karma)
+    (Currently, joes@ and pgollucci@ are active and have karma)
 
 12. Upload the package to CPAN. Doublecheck that the md5 checksum
    received from PAUSE is correct.