forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r410213 - in /forrest/trunk/site-author/content/xdocs/procedures/release: How_to_release.xml propose_release_plan.txt
Date Tue, 30 May 2006 08:05:25 GMT
Author: crossley
Date: Tue May 30 01:05:25 2006
New Revision: 410213

URL: http://svn.apache.org/viewvc?rev=410213&view=rev
Log:
Clarify how to tell when a plugin uses Locationmap.
Clarify previous fixme about replacing site:v0.90 references.

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

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?rev=410213&r1=410212&r2=410213&view=diff
==============================================================================
--- 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 Tue May
30 01:05:25 2006
@@ -261,7 +261,13 @@
                     <p>Adjust version-numbers in site.xml.</p>
                     <fixme author="fso">This used to be the comment: 'Do global replace
throughout docs_0_80 to replace the string
                         ="site:v0.70 with ="site:v0.80' but this needs checking.</fixme>
-                    <fixme author="dc">Perhaps you are talking about something else.
I meant that when we copy the docs to become the next -dev (i.e. this time docs_0_90) then
we need to replace all "site:" references (i.e. ="site:v0.80 with ="site:v0.90'). If you can
see a better way, then great.</fixme>
+                    <fixme author="dc">Perhaps you are talking about something else.
+                      I meant that when we copy the docs to become the next -dev (i.e.
+                      this time docs_0_90) then we need to replace all "site:" references
+                      (i.e. ="site:v0.80 with ="site:v0.90'). If you can see a better way,
then great.
+                     Maybe dropping the v0.x prefix will cause it to use the most recent
doc,
+                     e.g. use site:buildPlugin rather than site:v0.90/howto/buildplugin.
+                  </fixme>
                     
                 </li>
                 
@@ -380,8 +386,8 @@
                 <li>
                     <p>Ensure that each plugin that uses the locationmap has its "release
version" set to 0.8 or
                         more.</p>
-                    <fixme author="fso">Add the steps required to find that plugins
that use locationmap and set the
-                        version number. Is that 0.8 only or will this be a permanent job.</fixme>
+                    <p>If a plugin has a locationmap.xml file or uses "lm:" references
in its *.xmap,
+                     then it is using locationmap. See <a href="site:buildPlugin">buildPlugin</a>.</p>
                 </li>
                 <li>
                     <p>Edit 4 files in tools/forrestbar to update the version number
to match the new release: -

Modified: forrest/trunk/site-author/content/xdocs/procedures/release/propose_release_plan.txt
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/propose_release_plan.txt?rev=410213&r1=410212&r2=410213&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/release/propose_release_plan.txt (original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/propose_release_plan.txt Tue
May 30 01:05:25 2006
@@ -1,9 +1,17 @@
+FIXME: http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html
+incorporate that into this
+
 Subject: [VOTE] Release Plan for Forrest x.xx
 
 We are about to work on releasing a new version of Forrest. 
 Below I have proposed the important milestones. 
-Please check with your schedules and comment, 
-after that we'll vote on this.
+
+Please check with your time schedules and comment.
+We want to have as many people available as possible
+to test the release candidate. So we can adjust the
+time schedule a bit.
+
+Please vote on this release plan.
    
 Proposed Java version to test this release is [Version].  
 
@@ -39,5 +47,5 @@
 - Scheduled release Date [Date]
    [www.timeanddate.com-URL]
 
-For background info on this step and the relaese process in general see 
-http://forrest.apache.org/procedures/release/How_to_release.html#PrepRelPlan
\ No newline at end of file
+For background info on this step and the release process in general see 
+http://forrest.apache.org/procedures/release/How_to_release.html#PrepRelPlan



Mime
View raw message