forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r409929 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Date Sun, 28 May 2006 05:40:54 GMT
Author: crossley
Date: Sat May 27 22:40:54 2006
New Revision: 409929

Another task in the Cleanup is to create a new plugins directory
in the forrest/site SVN for the next develoment phase.


Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
--- 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 Sat May
27 22:40:54 2006
@@ -305,16 +305,6 @@
                     <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>
-                <li>
-                    <p> Rename the deployed plugins directory by issuing the following
commands at the command line </p>
-                    <source>cd /svn/asf/forrest-site
-svn update
-svn mv plugins/0.8-dev plugins/0.8
-svn mkdir plugins/0.9-dev
-svn status
-svn commit</source>
-                    <fixme author="fso">Issue them where and to what end?</fixme>
-                </li>
                 <li>Commit all of the above changes.</li>
@@ -667,6 +657,12 @@
                 <li>Commit all of the above changes.</li>
                 <li><p>Remove old dist files from the /www/
                     They have already been automatically archived at</p></li>
+                <li>Create a new plugins directory in the forrest/site SVN for the
+                  next development phase:
+                  <source>
+svn mkdir
+                  </source>
+                </li>
                 <li><p>Do some Jira administration (need to be in the jira-administrators
                 <fixme author="fso">Does it make sense to pass this job to the Jira-role?</fixme>

View raw message