[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-cvs
Subject:    svn commit: r1830044 - /httpd/site/trunk/content/dev/release.mdtext
From:       druggeri () apache ! org
Date:       2018-04-25 1:35:01
Message-ID: 20180425013502.C58CD3A00B7 () svn01-us-west ! apache ! org
[Download RAW message or body]

Author: druggeri
Date: Wed Apr 25 01:35:01 2018
New Revision: 1830044

URL: http://svn.apache.org/viewvc?rev=1830044&view=rev
Log:
Add some notes about new scripts

Modified:
    httpd/site/trunk/content/dev/release.mdtext

Modified: httpd/site/trunk/content/dev/release.mdtext
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/dev/release.mdtext?rev=1830044&r1=1830043&r2=1830044&view=diff
 ==============================================================================
--- httpd/site/trunk/content/dev/release.mdtext (original)
+++ httpd/site/trunk/content/dev/release.mdtext Wed Apr 25 01:35:01 2018
@@ -147,7 +147,11 @@ confidence in the release that it will n
 Once the tree has been suitably tested by the RM and any other interested
 parties, they should "roll" a candidate tarball for potential release.
 
-Key points:
+The process is largely automated through shell scripts. The exact commands
+needed to perform a release are captured inside, so consider reading the
+scripts and comments within for a complete understandig of the process.
+
+Key points the automation handles:
 
 1. Ensure the Copyright date reflects the current year in the NOTICE,
 docs/manual/style/latex/latex.xsl, and docs/manual/style/xsl/common.xsl
@@ -173,19 +177,78 @@ transformations are up to date.
 
 1. Run the svn.apache.org/repos/asf/httpd/site/trunk/tools/release.sh script.
 
-1. Commit the generated release tarballs and signatures to the subversion
+1. Generate a proposed release announcement and CHANGES entry
+
+1. Commit the generated release tarballs, signatures and proposed announcements
+ to the subversion
 https://dist.apache.org/repos/dist/dev/httpd/ repository.
 
 1. Email dev@httpd.apache.org with a [VOTE] Release X.Y.Z to call for
 testing and votes on this candidate.
 
-# What can I call this release? #
+1. When the vote has concluded, the tarballs and signatures can be pushed
+to the release distribution mirror
+
+1. After a 24 to 48 hour delay for the mirrors to replicate the data, the
+release can be announced with any pending security announcements as well.
+
 
-At this point, this tarball/archive is not yet a release.
+The automated workflow is:
 
-Based on the communities confidence in the code, the next step is to issue
-a release vote as alpha, beta or general availability (GA) candidate. The
-Apache HTTP Server Project has three classifications for its releases:
+    TAG="2.4.33"
+    ME="Release Manager"
+    KEY_EMAIL='my_personal@address.com'
+    ASF_EMAIL='asfid@apache.org'
+    
+    # Get the tooling
+    svn co https://svn.apache.org/repos/asf/httpd/site/trunk/tools tools
+    cd tools
+    
+    # Tag a specific version in the 2.4.x branch
+    ./tag.sh 2.4.x $TAG /tmp/foo
+    
+    # Generate a release tarball (including dependencies for testing)
+    # signed with the signer email address. This will be placed in
+    # your current directory
+    ./release.sh --latestapxxx --tag $TAG '' httpd-2.4 $TAG "$KEY_EMAIL"
+    
+    # Send the proposed release in $CWD off to the dev dist location
+    ./push.sh . $TAG dev
+    
+    # Generate a vote thread email to send to dev@
+    echo "
+    Subject: [VOTE] Release httpd-$TAG
+    
+    Hi, all;
+       Please find below the proposed release tarball and signatures:
+    https://dist.apache.org/repos/dist/dev/httpd/
+    
+    I would like to call a VOTE over the next few days to release this candidate \
tarball as $TAG: +    [ ] +1: It's not just good, it's good enough!
+    [ ] +0: Let's have a talk.
+    [ ] -1: There's trouble in paradise. Here's what's wrong.
+    
+    The computed digests of the tarball up for vote are:
+    `grep '^' httpd-$TAG.tar.gz.md5 httpd-$TAG.tar.gz.sha* | sed -e \
's/.*.tar.gz.//g' -e 's/:/: /g'` +    "
+    
+    # Wait for vote
+    
+    # Successful vote: Push to the mirrors for distribution
+    ./push.sh . $TAG dist
+    
+    # Wait for mirrors. Verify no mangling of CHANGES/announcement happened
+    # with the scripts (they use the files in the dist repo for sending)
+    
+    # Generate and send release and security announcements
+    ./announce.sh $TAG "$ASF_EMAIL" "$ME"
+
+# What can I call this release? #
+
+Based on the community's confidence in the code, the potential release is
+tagged as alpha, beta or general availability (GA) and the candidate and
+is voted in that manner. The Apache HTTP Server Project has three
+classifications for its releases:
 
 - Alpha
 
@@ -235,6 +298,9 @@ patches MUST be made available alongside
 
 # How do we make it public? #
 
+Remember, the automation handles the moving and announcements this for
+the most part.
+
 Once the release has reached the highest-available designation (as deemed
 by the RM), the release can be moved to the httpd distribution directory on
 apache.org. The release tarballs and signatures can be svn mv'ed from the


[prev in list] [next in list] [prev in thread] [next in thread]