forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r190533 - /forrest/trunk/etc/RELEASE_PROCESS.txt
Date Tue, 14 Jun 2005 00:01:09 GMT
Author: crossley
Date: Mon Jun 13 17:01:08 2005
New Revision: 190533

URL: http://svn.apache.org/viewcvs?rev=190533&view=rev
Log:
Tweak notes about gpg and md5.

Modified:
    forrest/trunk/etc/RELEASE_PROCESS.txt

Modified: forrest/trunk/etc/RELEASE_PROCESS.txt
URL: http://svn.apache.org/viewcvs/forrest/trunk/etc/RELEASE_PROCESS.txt?rev=190533&r1=190532&r2=190533&view=diff
==============================================================================
--- forrest/trunk/etc/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/etc/RELEASE_PROCESS.txt Mon Jun 13 17:01:08 2005
@@ -56,7 +56,6 @@
 without committing anything. This ensures a good release candidate.
 
 
-
 - Update your release checkout to reflect last minute changes
 
     1. cd to the 'Forrest_Release'-directory
@@ -123,6 +122,8 @@
    Note: If you change the setting in the system properties, you have to logout and login

    again for the changes to become effective.
 
+ - Take note of the SVN revision number of your trunk.
+
  - Change to directory main and run 'build release-dist' to generate the
    distributions on a UNIX machine.
    - Two archives are created: apache-forrest-X.Y.tar.gz apache-forrest-X.Y.zip
@@ -145,14 +146,19 @@
    Not going to try to explain, but here is some info:
     http://wiki.apache.org/incubator/SigningReleases
     http://forrest.apache.org/mirrors.cgi#verify
-   Create the *.md5 and *.asc files. Here is one example:
+   Create the *.asc and *.md5 files. Here is one example:
+
    gpg --recv-key <myKey>
-   gpg --output crossley-apache-forrest-0.7.tar.gz.asc \
-       --detach-sig --armor apache-forrest-0.7.tar.gz
+   gpg --output apache-forrest-0.7rc1.tar.gz.asc \
+       --detach-sig --armor apache-forrest-0.7rc1.tar.gz
    gpg --verify crossley-apache-forrest-0.7.tar.gz.asc \
-       apache-forrest-0.7.tar.gz
-   openssl dgst -md5 -out crossley-apache-forrest-0.7.tar.gz.md5 \
-       apache-forrest-0.7.tar.gz
+       apache-forrest-0.7rc1.tar.gz
+   ... should say "Good signature from ..."
+
+   openssl dgst -md5 -out apache-forrest-0.7.tar.gz.md5 \
+       apache-forrest-0.7rc1.tar.gz
+   md5sum apache-forrest-0.7rc1.tar.gz
+   ... output should match that of the md5 file.
 
  - Create a maintenance branch in SVN with
     svn copy -m "Create the x.y release branch from r#####" \
@@ -162,6 +168,8 @@
    and 'r#####' is the SVN revision number that the branch was created from
    which was the revision that the release candidates were generated from.
    See http://svn.apache.org/repos/asf/forrest/branches/
+   If someone has done a commit before you get to do it, then specify
+   the revision number with -r
 
  - Test the actual distribution on various platforms.
    - Upload the release candidates and signatures to a committer's webspace.



Mime
View raw message