svn commit: r890684 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

[cr...@apache.org]

Author: crossley
Date: Tue Dec 15 08:25:41 2009
New Revision: 890684

URL: http://svn.apache.org/viewvc?rev=890684&view=rev
Log:
Some text tweaks.

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?rev=890684&r1=890683&r2=890684&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 Dec 15 08:25:41 2009
@@ -164,7 +164,7 @@
         <li>The project made good progress towards fixing the Blockers and applying the outstanding patches.</li>
         <li>The documentation content is ready.</li>
         <li>Plugins have been reviewed and deployed as necessary. Some perhaps need to
-          go through a release process. This should happen independently of the release process.
+          go through a release process. This should happen independently of the core release process.
         </li>
         <li>Supporting products (e.g. Ant, Xerces) should have been updated well before this
                 stage. Do not attempt such upgrades too close to the release, as it
@@ -319,14 +319,15 @@
       </p>
       <note>
         There are various reasons for voting on the Release Plan, e.g. makes
-        people aware that a code-freeze is about to happen; encourage them to
-        get involved with the release; ensure that the date is suitable and
+        people aware that a code-freeze is about to happen; draws attention to
+        the release process; encourages people to get involved; ensures that the
+        date is suitable and
         people will be around to test and then vote on the actual release. This
         ensures that it is the PMC as a whole that prepares and issues the
         release, rather than an individual. Such procedures give us the
         protection accorded by the ASF being a corporation. See a good
-        discussion <a href="http://marc.theaimsgroup.com/?t=114296877800003" rel="nofollow">in
-        the archives</a>.
+        discussion on the cocoon-dev list:
+        <a href="http://marc.theaimsgroup.com/?t=114296877800003" rel="nofollow">Re: Voting on releases?</a>
       </note>
     </section>
     <section id="PrepCodeBase">
@@ -692,7 +693,7 @@
             This will be used later for the svn log message when the branch is
             created. Also it is helpful for ensuring that no new commits have
             been made, i.e. people forgetting the code freeze. From here on
-            watch the svn@ list.
+            carefully watch the svn@ list.
           </p></li>
         <li><p>Cleanup your working copy to remove any extra files.</p>
           <source>
@@ -1005,7 +1006,7 @@
           </p>
           <p>
             See <a href="http://www.apache.org/mirrors/">Status of mirrors</a>.
-            It is a very useful service and fun to watch. See the "age histogram"i
+            It is a very useful service and fun to watch. See the "age histogram"
             near the bottom.
           </p>
           <p>

Re: Java settings

[David Crossley <cr...@apache.org>]

Brian M Dube wrote:
> >     forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
> 
> This edit prompted me to browse through this file for the first time
> in a while. I didn't see it noted anywhere to turn off debug symbols
> and to turn on code optimization as part of the test and release
> cycle. Our code base is tiny enough that I don't think this matters
> for us, but does anyone know if our major dependencies (such as
> Cocoon) do this as part of their release? Do we want to for our code?

I don't know the answers to this, not being a real Java person.

In $FORREST_HOME/etc/cocoon_upgrade/local.build.properties
---------
compiler=modern
compiler.debug=on
compiler.optimize=on
compiler.deprecation=off
compiler.nowarn=on
source.vm=1.4
---------

Please do whatever you reckon will assist.

-David

Java settings (was Re: svn commit: r890684 - /forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml)

[Brian M Dube <bd...@apache.org>]

On Tue, Dec 15, 2009 at 08:25:42AM -0000, crossley@apache.org wrote:
> Author: crossley
> Date: Tue Dec 15 08:25:41 2009
> New Revision: 890684
> 
> URL: http://svn.apache.org/viewvc?rev=890684&view=rev
> Log:
> Some text tweaks.
> 
> Modified:
>     forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml

This edit prompted me to browse through this file for the first time
in a while. I didn't see it noted anywhere to turn off debug symbols
and to turn on code optimization as part of the test and release
cycle. Our code base is tiny enough that I don't think this matters
for us, but does anyone know if our major dependencies (such as
Cocoon) do this as part of their release? Do we want to for our code?

Brian