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

[jf...@apache.org]

Author: jfthomps
Date: Wed Dec 12 18:57:24 2012
New Revision: 1420918

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

Added:
    vcl/site/trunk/content/dev/releaseprocedures231.mdtext
      - copied, changed from r1419792, vcl/site/trunk/content/dev/releaseprocedures.mdtext

Copied: vcl/site/trunk/content/dev/releaseprocedures231.mdtext (from r1419792, vcl/site/trunk/content/dev/releaseprocedures.mdtext)
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/dev/releaseprocedures231.mdtext?p2=vcl/site/trunk/content/dev/releaseprocedures231.mdtext&p1=vcl/site/trunk/content/dev/releaseprocedures.mdtext&r1=1419792&r2=1420918&rev=1420918&view=diff
==============================================================================
--- vcl/site/trunk/content/dev/releaseprocedures.mdtext (original)
+++ vcl/site/trunk/content/dev/releaseprocedures231.mdtext Wed Dec 12 18:57:24 2012
@@ -1,4 +1,4 @@
-Title: VCL Release Procedures
+Title: VCL Release Procedures - 2.3.1 ToDo
 Notice:    Licensed to the Apache Software Foundation (ASF) under one
            or more contributor license agreements.  See the NOTICE file
            distributed with this work for additional information
@@ -18,15 +18,15 @@ Notice:    Licensed to the Apache Softwa
 
 # Prerequisites: Things that must be done before a release
 
-* all items from the JIRA roadmap for the release must be completed or
-moved to a future release
-* ALL human readable files must contain the Apache license header
+* <s>all items from the JIRA roadmap for the release must be completed or
+moved to a future release</s>
+* <s>ALL human readable files must contain the Apache license header
     * this includes style sheets, test code, and documentation - when in
 	 doubt, add a header
     * files that are part of other software packages that are bundled with 
 	 a release must not contain the header (unless that software is also ASF 
-	 software) and should be clearly documented as being bundled software
-* LICENSE and NOTICE files should be reviewed
+	 software) and should be clearly documented as being bundled software</s>
+* <s>LICENSE and NOTICE files should be reviewed
     * LICENSE: This file should have the Apache License at the top of it; 
 	 any third party artifacts or documents included in the release should 
 	 have their licenses included in this file along with a clear explanation 
@@ -35,25 +35,25 @@ moved to a future release
 	 statements any third party licenses may require. A typical NOTICE 
 	 document at a minimum includes a copyright and attribution statement for 
 	 The Apache Software Foundation. Nothing else belongs in the NOTICE document.
-    * Make sure copyright date is correct in NOTICE file
-* Files containing the VCL version should be updated to the version being 
+    * Make sure copyright date is correct in NOTICE file</s>
+* <s>Files containing the VCL version should be updated to the version being 
 released
     * The backend Perl files contain a line defining a $VERSION variable, 
-	 this should be updated in every file
-* documentation on how to upgrade from a previous release must be created
+	 this should be updated in every file</s>
+* <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)
+	 (don't forget steps/scripts to upgrade the database schema)</s>
 * RELEASE_NOTES file needs to be updated and should contain:
-    * release version
+    * <s>release version
     * an intro to VCL
-    * a brief description of the aims of VCL
+    * a brief description of the aims of VCL</s>
     * a brief roadmap of VCL and how this release fits in to it
-    * a list of ways for users to get involved
-    * a description of how users can submit issues
-* the README file must also contain all dependencies (this includes PHP, 
+    * <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, 
 Perl, MySQL versions in addition to perl and php modules, dojo, etc.) for 
 running VCL, any changes in dependencies since the last release must be 
-listed in the CHANGLOG file
+listed in the CHANGLOG file</s>
 * generate a CHANGELOG file
     * go to the [Create Release Notes][1] page of the JIRA site
     * select the release version
@@ -62,27 +62,27 @@ listed in the CHANGLOG file
     * scroll down to **Edit/Copy Release Notes**
     * copy/paste the contents to a new section in the CHANGELOG file
     * make sure to add any changes in the dependencies since the last release
-* make sure INSTALLATION file is up to date with content from Confluence on 
-how to install each part
-* ensure LICENSE, NOTICE, RELEASE_NOTES, CHANGELOG, INSTALLATION, UPGRADE, 
+* <s>make sure INSTALLATION file is up to date with content from Confluence on 
+how to install each part</s>
+* <s>ensure LICENSE, NOTICE, RELEASE_NOTES, CHANGELOG, INSTALLATION, UPGRADE, 
 and README files are in top level directory of trunk (or the branch that 
-will be used for the release)
-* an export from HEAD should result in a directory tree with all files and 
-directories having appropriate permissions
-* release manager's GPG signing key must be in KEYS file in toplevel 
-directory of SVN (one above trunk)
-* a release/download page needs to be created for the specific release 
+will be used for the release)</s>
+* <s>an export from HEAD should result in a directory tree with all files and 
+directories having appropriate permissions</s>
+* <s>release manager's GPG signing key must be in KEYS file in toplevel 
+directory of SVN (one above trunk)</s>
+* <s>a release/download page needs to be created for the specific release 
 containing:
     * link to release artifact (link to a mirror)
     * link to signatures and checksums (link directly to apache.org)
     * steps explaining how to verify artifact using signatures and checksums
     * either a link to release notes or contain them inline
-    * either a link to a change log or contain it inline
+    * either a link to a change log or contain it inline</s>
 * a decision needs to be made determining which, if any, previously released 
 artifacts should be removed from the main distribution site after this 
 release is completed
-* make sure the index.php file from the web code has the correct VCL 
-version at the top of it
+* <s>make sure the index.php file from the web code has the correct VCL 
+version at the top of it</s>
 
 # Steps to create a release candidate artifact