svn commit: r843269 - in /websites/staging/vcl/trunk/content: ./ dev/releaseprocedures231.html

[bu...@apache.org]

Author: buildbot
Date: Thu Dec 20 20:43:56 2012
New Revision: 843269

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/dev/releaseprocedures231.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Dec 20 20:43:56 2012
@@ -1 +1 @@
-1424079
+1424692

Modified: websites/staging/vcl/trunk/content/dev/releaseprocedures231.html
==============================================================================
--- websites/staging/vcl/trunk/content/dev/releaseprocedures231.html (original)
+++ websites/staging/vcl/trunk/content/dev/releaseprocedures231.html Thu Dec 20 20:43:56 2012
@@ -113,11 +113,11 @@ released<ul>
  (don't forget steps/scripts to upgrade the database schema)</s></li>
 </ul>
 </li>
-<li>RELEASE_NOTES file needs to be updated and should contain:<ul>
+<li><s>RELEASE_NOTES file needs to be updated and should contain:</s><ul>
 <li><s>release version</li>
 <li>an intro to VCL</li>
 <li>a brief description of the aims of VCL</s></li>
-<li>a brief roadmap of VCL and how this release fits in to it</li>
+<li><s>a brief roadmap of VCL and how this release fits in to it</s></li>
 <li><s>a list of ways for users to get involved</li>
 <li>a description of how users can submit issues</s></li>
 </ul>
@@ -162,7 +162,7 @@ version at the top of it</s></li>
 </ul>
 <h1 id="steps-to-create-a-release-candidate-artifact">Steps to create a release candidate artifact</h1>
 <ul>
-<li>A tag for the release candidate needs to be created in subversion. It 
+<li><s>A tag for the release candidate needs to be created in subversion. It 
 should be created under the <strong>tags</strong> directory of the repository and should be 
 named <strong>release-W.X.Y-RCZ</strong> (with Z being the release candidate number, starting 
 with 1 and with .Y only being included if Y &gt; 0)</li>
@@ -189,33 +189,33 @@ with 1 and with .Y only being included i
 </li>
 <li>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)</li>
+to cut down on archive storage and mirroring bandwidth)</s></li>
 </ul>
 <h1 id="community-and-pmc-voting-process">Community and PMC voting process</h1>
 <ul>
-<li>release manager should start a <a href="http://www.apache.org/foundation/voting.html#ReleaseVotes">VOTE</a> thread on the dev list; <a href="http://markmail.org/message/ysdor5uddhviawln">this is a 
+<li><s>release manager should start a <a href="http://www.apache.org/foundation/voting.html#ReleaseVotes">VOTE</a> thread on the dev list; <a href="http://markmail.org/message/ysdor5uddhviawln">this is a 
 good example</a></li>
 <li>the release manage's vote should be posted in a separate message from the 
 one calling for the vote</li>
 <li>the VOTE thread should be ended with a reply post including [RESULT] in the 
 subject; <a href="http://markmail.org/message/kanwckkfrnbcs2s7">this is a good example</a> except that it is missing the [RESULT] part from 
-the subject</li>
+the subject</s></li>
 </ul>
 <h1 id="steps-to-make-the-rc-available-as-a-release-artifact">Steps to make the RC available as a release artifact</h1>
 <ul>
-<li>create a tag for the release from the approved RC tag (svn copy from RC 
+<li><s>create a tag for the release from the approved RC tag (svn copy from RC 
 tag to new release tag)</li>
 <li>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 &gt; 0) - 
 untar old one, rename director to not have RC part, create new tarball</li>
 <li>sign the file with GPG</li>
-<li>create md5 and sha1 sum files</li>
+<li>create md5 and sha1 sum files</s></li>
 </ul>
 <h1 id="steps-to-make-release-artifact-available-to-users">Steps to make release artifact available to users</h1>
 <ul>
-<li>place the release artifact, sums, and signature in 
+<li><s>place the release artifact, sums, and signature in 
 /www/www.apache.org/dist/vcl on people.apache.org</li>
-<li>ensure the artifact has permissions 664 and is owned by the vcl group</li>
+<li>ensure the artifact has permissions 664 and is owned by the vcl group</s></li>
 <li>wait 24 hours for the artifact to propagate to the mirrors before 
 announcing the release<ul>
 <li>ideally, a test download should be done from the mirror and a check