You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by bu...@apache.org on 2014/08/22 17:03:32 UTC

svn commit: r920147 - in /websites/staging/httpd/trunk/content: ./ dev/release.html

Author: buildbot
Date: Fri Aug 22 15:03:32 2014
New Revision: 920147

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 Fri Aug 22 15:03:32 2014
@@ -1 +1 @@
-1612306
+1619829

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 Fri Aug 22 15:03:32 2014
@@ -117,7 +117,9 @@ our community because it takes a fair am
 release. If you feel lucky, a release could be distributed without testing,
 but our experience has shown that this leads to a higher number of <em>dud</em>
 releases. In general, our experience has shown that a well-coordinated
-release fares better than non-coordinated releases.</p>
+release fares better than non-coordinated releases.  In all cases, three
++1 votes, and more +1 than -1 votes from PMC members are required for a
+release candidate to be designated as a release.</p>
 <h1 id="when-do-i-know-if-it-is-a-good-time-to-release">When do I know if it is a good time to release?</h1>
 <p>Generally speaking, when some useful changes have been applied since the
 last release and there are no showstoppers left to be resolved. It is our
@@ -184,32 +186,38 @@ parties, they should "roll" a candidate 
 <p>Key points:</p>
 <ol>
 <li>
-<p>Execute <code>./build.sh all</code> in case of the 2.2.x documentation and
-<code>./build.sh all convmap</code> in case of the 2.2.x documentation to ensure that
-the documentation transformations are up to date.</p>
+<p>Ensure the Copyright date reflects the current year in the NOTICE,
+docs/manual/style/latex/latex.xsl, and docs/manual/style/xsl/common.xsl
+files.</p>
+</li>
+<li>
+<p>Execute <code>./build.sh all convmap</code> to ensure that the documentation
+transformations are up to date.</p>
 </li>
 <li>
 <p>Ensure that the RM's PGP/GPG key is in the httpd-dist/KEYS file.</p>
 </li>
 <li>
-<p>Set <code>AP_SERVER_DEVBUILD_BOOLEAN</code> to <code>0</code> in <code>include/ap_release.h</code> in
-case of 2.2.x and set <code>AP_SERVER_ADD_STRING</code> to <code>""</code> in case of 2.2.x.</p>
+<p>Set <code>AP_SERVER_DEVBUILD_BOOLEAN</code> to <code>0</code> in <code>include/ap_release.h</code>.</p>
 </li>
 <li>
 <p>Create an official X.Y.Z tag based on the candidate tree.</p>
 </li>
 <li>
-<p>Revert the changes done to <code>include/ap_release.h</code> and bump
-<code>AP_SERVER_PATCHLEVEL_NUMBER</code>.</p>
+<p>Revert the change to <code>include/ap_release.h</code> setting 
+<code>AP_SERVER_DEVBUILD_BOOLEAN</code> back to <code>1</code>, and bump <code>AP_SERVER_PATCHLEVEL_NUMBER</code></p>
 </li>
 <li>
 <p>Bump <code>ENTITY httpd.patch</code> in <code>docs/manual/style/version.ent</code>.</p>
 </li>
 <li>
+<p>Add the corresponding version placeholder in CHANGES.</p>
+</li>
+<li>
 <p>Note the tag date in the STATUS file.</p>
 </li>
 <li>
-<p>Run the httpd/site/trunk/tools/release.sh script.</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