svn commit: r1424692 - /vcl/site/trunk/content/dev/releaseprocedures231.mdtext

[jf...@apache.org]

Author: jfthomps
Date: Thu Dec 20 20:43:51 2012
New Revision: 1424692

URL: http://svn.apache.org/viewvc?rev=1424692&view=rev
Log:
CMS commit to vcl by jfthomps

Modified:
    vcl/site/trunk/content/dev/releaseprocedures231.mdtext

Modified: vcl/site/trunk/content/dev/releaseprocedures231.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/dev/releaseprocedures231.mdtext?rev=1424692&r1=1424691&r2=1424692&view=diff
==============================================================================
--- vcl/site/trunk/content/dev/releaseprocedures231.mdtext (original)
+++ vcl/site/trunk/content/dev/releaseprocedures231.mdtext Thu Dec 20 20:43:51 2012
@@ -43,11 +43,11 @@ released
 * <s>documentation on how to upgrade from a previous release must be created
     * if appropriate, scripts to help users upgrade should be created 
 	 (don't forget steps/scripts to upgrade the database schema)</s>
-* RELEASE_NOTES file needs to be updated and should contain:
+* <s>RELEASE_NOTES file needs to be updated and should contain:</s>
     * <s>release version
     * an intro to VCL
     * a brief description of the aims of VCL</s>
-    * a brief roadmap of VCL and how this release fits in to it
+    * <s>a brief roadmap of VCL and how this release fits in to it</s>
     * <s>a list of ways for users to get involved
     * a description of how users can submit issues</s>
 * <s>the README file must also contain all dependencies (this includes PHP, 
@@ -86,7 +86,7 @@ version at the top of it</s>
 
 # Steps to create a release candidate artifact
 
-* A tag for the release candidate needs to be created in subversion. It 
+* <s>A tag for the release candidate needs to be created in subversion. It 
 should be created under the **tags** directory of the repository and should be 
 named **release-W.X.Y-RCZ** (with Z being the release candidate number, starting 
 with 1 and with .Y only being included if Y > 0)
@@ -107,33 +107,33 @@ with 1 and with .Y only being included i
     * [This document][2] contains information on how to sign the tarball
 * distribute the RC through the release manager's personal web space on 
 people.apache.org (RC are not to be release from the main distribution area 
-to cut down on archive storage and mirroring bandwidth)
+to cut down on archive storage and mirroring bandwidth)</s>
 
 # Community and PMC voting process
 
-* release manager should start a [VOTE][3] thread on the dev list; [this is a 
+* <s>release manager should start a [VOTE][3] thread on the dev list; [this is a 
 good example][4]
 * the release manage's vote should be posted in a separate message from the 
 one calling for the vote
 * the VOTE thread should be ended with a reply post including [RESULT] in the 
 subject; [this is a good example][5] except that it is missing the [RESULT] part from 
-the subject
+the subject</s>
 
 # Steps to make the RC available as a release artifact
 
-* create a tag for the release from the approved RC tag (svn copy from RC 
+* <s>create a tag for the release from the approved RC tag (svn copy from RC 
 tag to new release tag)
 * create a copy of the approved RC artifact and name it 
 apache-VCL-X.Y.Z-incubating.tar.bz2 (the .Z should only be included if Z > 0) - 
 untar old one, rename director to not have RC part, create new tarball
 * sign the file with GPG
-* create md5 and sha1 sum files
+* create md5 and sha1 sum files</s>
 
 # Steps to make release artifact available to users
 
-* place the release artifact, sums, and signature in 
+* <s>place the release artifact, sums, and signature in 
 /www/www.apache.org/dist/vcl on people.apache.org
-* ensure the artifact has permissions 664 and is owned by the vcl group
+* ensure the artifact has permissions 664 and is owned by the vcl group</s>
 * wait 24 hours for the artifact to propagate to the mirrors before 
 announcing the release
     * ideally, a test download should be done from the mirror and a check