forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r1057127 - /forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml
Date Mon, 10 Jan 2011 08:53:45 GMT
Author: crossley
Date: Mon Jan 10 08:53:44 2011
New Revision: 1057127

URL: http://svn.apache.org/viewvc?rev=1057127&view=rev
Log:
Clarify the notes about final deploy, then incrementing version numbers.

Modified:
    forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml

Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml?rev=1057127&r1=1057126&r2=1057127&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/howto/howto-buildPlugin.xml Mon Jan
10 08:53:44 2011
@@ -386,14 +386,16 @@
         <p>
           When a plugin gains new functionality, then it will be dependent on a
           more recent version of Forrest. Deploy the plugin one final time
-          before implementing the new work. For example, if current release is
+          before implementing the new work. For example, if current Forrest release is
           0.7 then ...
         </p>
         <ul>
           <li>Review the docs and ensure any version numbers in text are "0.7"</li>
-          <li>Edit the plugin's descriptors to ensure that the "forrestVersion" is
0.7 and that the "version" is appropriate. </li>
+          <li>Edit the plugin's descriptors and build.xml file to ensure that the "forrestVersion"
is 0.7 and that the "version" is appropriate. </li>
           <li>Ensure that the "website" parameter includes "pluginDocs/plugins_0_70"</li>
-          <li>Edit status.xml to set the release date. Ensure that the changes notes
are complete.</li>
+          <li>Edit status.xml to ensure that the changes notes are complete.</li>
+          <li>Do <code>'ant deploy'</code> and <code>'ant release'</code>
again
+            to get any final minor changes deployed.</li>
         </ul>
         <p>
           Now the plugin gains functionality that binds it to 0.8-dev (e.g.
@@ -402,11 +404,12 @@
         <ul>
           <li>Review the docs and ensure any version numbers in text are
              "0.8"</li>
-          <li>Edit the plugin's descriptors to ensure that the "forrestVersion" is
+          <li>Edit the plugin's descriptors and build.xml file to ensure that the "forrestVersion"
is
              0.8 and that the "version" is incremented. </li>
           <li>Ensure that the "website" parameter includes "pluginDocs/plugins_0_80"</li>
-          <li>Edit status.xml to add a new section and set the release date.
-             Start adding changes notes.</li>
+          <li>Edit status.xml to add a new section and set the release date to "not-yet-released".
+             Start adding changes notes and the new functionality.</li>
+          <li>When ready do the plugin release process, and do <code>'ant deploy'</code>
and <code>'ant release'</code> etc.</li>
         </ul>
       </section>
       <section id="register">



Mime
View raw message