svn commit: r1619829 - /httpd/site/trunk/content/dev/release.mdtext

[wr...@apache.org]

Author: wrowe
Date: Fri Aug 22 15:03:27 2014
New Revision: 1619829

URL: http://svn.apache.org/r1619829
Log:
Refresh the instructions, dropping 2.0 and catching some gotchas

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=1619829&r1=1619828&r2=1619829&view=diff
==============================================================================
--- httpd/site/trunk/content/dev/release.mdtext (original)
+++ httpd/site/trunk/content/dev/release.mdtext Fri Aug 22 15:03:27 2014
@@ -69,7 +69,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 *dud*
 releases. In general, our experience has shown that a well-coordinated
-release fares better than non-coordinated releases.
+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.
 
 # When do I know if it is a good time to release? #
 
@@ -147,25 +149,29 @@ parties, they should "roll" a candidate 
 
 Key points:
 
-1. Execute `./build.sh all` in case of the 2.2.x documentation and
-`./build.sh all convmap` in case of the 2.2.x documentation to ensure that
-the documentation transformations are up to date.
+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
+files.
+ 
+1. Execute `./build.sh all convmap` to ensure that the documentation
+transformations are up to date.
 
 1. Ensure that the RM's PGP/GPG key is in the httpd-dist/KEYS file.
 
-1. Set `AP_SERVER_DEVBUILD_BOOLEAN` to `0` in `include/ap_release.h` in
-case of 2.2.x and set `AP_SERVER_ADD_STRING` to `""` in case of 2.2.x.
+1. Set `AP_SERVER_DEVBUILD_BOOLEAN` to `0` in `include/ap_release.h`.
 
 1. Create an official X.Y.Z tag based on the candidate tree.
 
-1. Revert the changes done to `include/ap_release.h` and bump
-`AP_SERVER_PATCHLEVEL_NUMBER`.
+1. Revert the change to `include/ap_release.h` setting 
+`AP_SERVER_DEVBUILD_BOOLEAN` back to `1`, and bump `AP_SERVER_PATCHLEVEL_NUMBER`
 
 1. Bump `ENTITY httpd.patch` in `docs/manual/style/version.ent`.
 
+1. Add the corresponding version placeholder in CHANGES.
+
 1. Note the tag date in the STATUS file.
 
-1. Run the httpd/site/trunk/tools/release.sh script.
+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
 https://dist.apache.org/repos/dist/dev/httpd/ repository.