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

List:       apache-cvs
Subject:    svn commit: r1028937 - in /websites/staging/httpd/trunk/content: ./ dev/release.html
From:       buildbot () apache ! org
Date:       2018-04-25 1:20:16
Message-ID: 20180425012016.B60943A00B7 () svn01-us-west ! apache ! org
[Download RAW message or body]

Author: buildbot
Date: Wed Apr 25 01:20:16 2018
New Revision: 1028937

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/dev/release.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Apr 25 01:20:16 2018
@@ -1 +1 @@
-1829619
+1830042

Modified: websites/staging/httpd/trunk/content/dev/release.html
==============================================================================
--- websites/staging/httpd/trunk/content/dev/release.html (original)
+++ websites/staging/httpd/trunk/content/dev/release.html Wed Apr 25 01:20:16 2018
@@ -219,7 +219,10 @@ confidence in the release that it will n
 <h1 id="how-to-do-a-release">How to do a release?<a class="headerlink" \
href="#how-to-do-a-release" title="Permanent link">&para;</a></h1>  <p>Once the tree \
has been suitably tested by the RM and any other interested  parties, they should \
                "roll" a candidate tarball for potential release.</p>
-<p>Key points:</p>
+<p>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.</p>
+<p>Key points the automation handles:</p>
 <ol>
 <li>
 <p>Ensure the Copyright date reflects the current year in the NOTICE,
@@ -256,19 +259,69 @@ transformations are up to date.</p>
 <p>Run the svn.apache.org/repos/asf/httpd/site/trunk/tools/release.sh script.</p>
 </li>
 <li>
-<p>Commit the generated release tarballs and signatures to the subversion
+<p>Generate a proposed release announcement and CHANGES entry</p>
+</li>
+<li>
+<p>Commit the generated release tarballs, signatures and proposed announcements
+ to the subversion
 https://dist.apache.org/repos/dist/dev/httpd/ repository.</p>
 </li>
 <li>
 <p>Email dev@httpd.apache.org with a [VOTE] Release X.Y.Z to call for
 testing and votes on this candidate.</p>
 </li>
+<li>
+<p>When the vote has concluded, the tarballs and signatures can be pushed
+to the release distribution mirror</p>
+</li>
+<li>
+<p>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.</p>
+</li>
 </ol>
+<p>The automated workflow is:</p>
+<p>````
+TAG="2.4.33"
+ME="Release Manager"
+KEY_EMAIL='my_personal@address.com'
+ASF_EMAIL='asfid@apache.org'</p>
+<h1 id="get-the-tooling">Get the tooling<a class="headerlink" \
href="#get-the-tooling" title="Permanent link">&para;</a></h1> +<p>svn co \
https://svn.apache.org/repos/asf/httpd/site/trunk/tools tools +cd tools</p>
+<h1 id="tag-a-specific-version-in-the-24x-branch">Tag a specific version in the \
2.4.x branch<a class="headerlink" href="#tag-a-specific-version-in-the-24x-branch" \
title="Permanent link">&para;</a></h1> +<p>./tag.sh 2.4.x $TAG /tmp/foo</p>
+<h1 id="generate-a-release-tarball-including-dependencies-for-testing">Generate a \
release tarball (including dependencies for testing)<a class="headerlink" \
href="#generate-a-release-tarball-including-dependencies-for-testing" \
title="Permanent link">&para;</a></h1> +<h1 \
id="signed-with-the-signer-email-address-this-will-be-placed-in">signed with the \
signer email address. This will be placed in<a class="headerlink" \
href="#signed-with-the-signer-email-address-this-will-be-placed-in" title="Permanent \
link">&para;</a></h1> +<h1 id="your-current-directory">your current directory<a \
class="headerlink" href="#your-current-directory" title="Permanent \
link">&para;</a></h1> +<p>./release.sh --latestapxxx --tag $TAG '' httpd-2.4 $TAG \
"$KEY_EMAIL"</p> +<h1 \
id="send-the-proposed-release-in-cwd-off-to-the-dev-dist-location">Send the proposed \
release in $CWD off to the dev dist location<a class="headerlink" \
href="#send-the-proposed-release-in-cwd-off-to-the-dev-dist-location" \
title="Permanent link">&para;</a></h1> +<p>./push.sh . $TAG dev</p>
+<h1 id="generate-a-vote-thread-email-to-send-to-dev">Generate a vote thread email to \
send to dev@<a class="headerlink" href="#generate-a-vote-thread-email-to-send-to-dev" \
title="Permanent link">&para;</a></h1> +<p>echo "
+Subject: [VOTE] Release httpd-$TAG</p>
+<p>Hi, all;
+   Please find below the proposed release tarball and signatures:
+https://dist.apache.org/repos/dist/dev/httpd/</p>
+<p>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.</p>
+<p>The computed digests of the tarball up for vote are:
+<code>grep '^' httpd-$TAG.tar.gz.md5 httpd-$TAG.tar.gz.sha* | sed -e \
's/.*.tar.gz.//g' -e 's/:/: /g'</code> +"</p>
+<h1 id="wait-for-vote">Wait for vote<a class="headerlink" href="#wait-for-vote" \
title="Permanent link">&para;</a></h1> +<h1 \
id="successful-vote-push-to-the-mirrors-for-distribution">Successful vote: Push to \
the mirrors for distribution<a class="headerlink" \
href="#successful-vote-push-to-the-mirrors-for-distribution" title="Permanent \
link">&para;</a></h1> +<p>./push.sh . $TAG dist</p>
+<h1 id="wait-for-mirrors-verify-no-mangling-of-changesannouncement-happened">Wait \
for mirrors. Verify no mangling of CHANGES/announcement happened<a class="headerlink" \
href="#wait-for-mirrors-verify-no-mangling-of-changesannouncement-happened" \
title="Permanent link">&para;</a></h1> +<h1 \
id="with-the-scripts-they-use-the-files-in-the-dist-repo-for-sending">with the \
scripts (they use the files in the dist repo for sending)<a class="headerlink" \
href="#with-the-scripts-they-use-the-files-in-the-dist-repo-for-sending" \
title="Permanent link">&para;</a></h1> +<h1 \
id="generate-and-send-release-and-security-announcements">Generate and send release \
and security announcements<a class="headerlink" \
href="#generate-and-send-release-and-security-announcements" title="Permanent \
link">&para;</a></h1> +<p>./announce.sh $TAG "$ASF_EMAIL" "$ME"
+````</p>
 <h1 id="what-can-i-call-this-release">What can I call this release?<a \
class="headerlink" href="#what-can-i-call-this-release" title="Permanent \
                link">&para;</a></h1>
-<p>At this point, this tarball/archive is not yet a release.</p>
-<p>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:</p>
+<p>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:</p>
 <ul>
 <li>
 <p>Alpha</p>
@@ -313,6 +366,8 @@ artifacts and must be generated from the
 release. If a patch is unavoidable for a specific platform, the applicable
 patches MUST be made available alongside the platform binaries.</p>
 <h1 id="how-do-we-make-it-public">How do we make it public?<a class="headerlink" \
href="#how-do-we-make-it-public" title="Permanent link">&para;</a></h1> +<p>Remember, \
the automation handles the moving and announcements this for +the most part.</p>
 <p>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]