Author: crossley
Date: Fri Dec  1 17:12:14 2006
New Revision: 481477

URL: http://svn.apache.org/viewvc?view=rev&rev=481477
Log:
Remember the dev note in upgrading_xy.xml

Modified:
    
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

Modified: 
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
URL: 
http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml?view=diff&rev=481477&r1=481476&r2=481477
==============================================================================
--- 
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml 
(original)
+++ 
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml 
Fri Dec  1 17:12:14 2006
@@ -71,6 +71,9 @@
               <li>The documentation content is ready.</li>
               <li><p>Relevant changes are listed in the site-author/status.xml 
and contributers have been attributed. Other changes are listed in the various 
plugins/status.xml files.</p>
               </li>
+              <li>Add relevant information to the
+                <a 
href="http://issues.apache.org/jira/browse/FOR-868";>upgrading notes</a>.
+              </li>
               <li><p>Major changes are listed in the site-author/status.xml 
using the "importance"
                 attribute. This will be used to generate the list of top 
changes for the Release Notes
                 and Announcement text.</p>
@@ -322,6 +325,7 @@
 
 
                 </li>
+                <li>Temporarily remove the "dev" note from 
upgrading_xy.xml</li>
                 <li>
                     <p>Edit the Forrest home page in the "News and events" 
section and add a text like:</p>
                     <source> Apache Forrest 0.xx was released on [Date]. 
[Important new features] </source>
@@ -374,7 +378,7 @@
                     <p>If there are any problems, focus on problems that 
prevent building and invite other commiters to
                         help you solve the problems.</p>
                     <note>It is not your job to fix bugs and code freeze 
should not commence with a broken trunk.</note>
-                    <p>If there are bugs that cannot be easily fixed, then 
call a halt to the release process and start
+                    <p>If there are bugs with the build system that cannot be 
easily fixed, then call a halt to the release process and start
                         a discussion on rescheduling options on the dev-list 
with the template <a
                             
href="rc_did_not_build_what_now.txt">rc_did_not_build_what_now.txt</a></p>
 
@@ -698,7 +702,8 @@
     |                        0.8-dev                        |
                         ]]></source>
                 </li>
-                <li>Edit site-author/conf/cli.xconf to exlude the old docs 
again.</li>
+                <li>Return the "dev" note to upgrading_xy.xml</li>
+                <li>Edit site-author/conf/cli.xconf to exclude the old docs 
again.</li>
                 <li>Commit all of the above changes.</li>
                 <li><p>Remove old dist files from the 
/www/www.apache.org/dist/forrest/ directory.
                     They have already been automatically archived at 
archive.apache.org/dist/forrest/</p></li>