svn commit: r190378 - /forrest/trunk/etc/RELEASE_PROCESS.txt

[fe...@apache.org]

Author: ferdinand
Date: Mon Jun 13 03:22:49 2005
New Revision: 190378

URL: http://svn.apache.org/viewcvs?rev=190378&view=rev
Log:
formatting and fixing some hasty conflict resolutions

Modified:
    forrest/trunk/etc/RELEASE_PROCESS.txt

Modified: forrest/trunk/etc/RELEASE_PROCESS.txt
URL: http://svn.apache.org/viewcvs/forrest/trunk/etc/RELEASE_PROCESS.txt?rev=190378&r1=190377&r2=190378&view=diff
==============================================================================
--- forrest/trunk/etc/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/etc/RELEASE_PROCESS.txt Mon Jun 13 03:22:49 2005
@@ -25,10 +25,10 @@
   ahead of time to avoid delays.
 
 - Announce the release plan to the dev list. Define when the code freeze
-  commences, when the vote ends etc. Use the last release plan as template:
-  http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html
-
-- Check out a fresh copy from SVN to make sure you have no local modifications,
+  commences, when the vote ends etc. See email templates at end-of-file.
+  Send a reminder when the code-freeze commences.
+  
+  - Check out a fresh copy from SVN to make sure you have no local modifications,
   especially those that might be hidden by svn:ignore settings.  
 
       1. Create a new empty directory 'Forrest_Release'
@@ -121,12 +121,14 @@
    Note: If you change the setting in the system properties, you have to logout and login 
    again for the changes to become effective.
 
- - Run 'build release-dist' to generate the distributions on a UNIX machine.
+ - Change to directory main and run 'build release-dist' to generate the distributions on a UNIX machine.
    - Two archives are created: apache-forrest-X.Y.tar.gz apache-forrest-X.Y.zip
    - Ignore the *.zip archive.
+   
  - Repeat that on a Windows machine.
    - Two archives are created: apache-forrest-X.Y.tar.gz apache-forrest-X.Y.zip
    - Ignore the *.tar.gz archive.
+ 
  Note: The reason for creating two separate archives is the line-endings
  dilemma between Windows and UNIX. SVN ensures correct line-endings
  on each operating system (as long as committers have been diligent when
@@ -312,32 +314,33 @@
 So we have approximately 6 days.
 
 Here are some hints:
-* Ensure that the compressed archive will unpack properly.
-* Verfiy the release, especially if you are a committer.
-* Follow the README.txt and index.html
-* Set environment variables.
-* Don't worry too much about minor bugs. We are looking
-for blockers, such as it will not run. Many known issues
-are recorded at our Jira, perhaps you can add more.
+
+  * Ensure that the compressed archive will unpack properly.
+  * Verfiy the release, especially if you are a committer.
+  * Follow the README.txt and index.html
+  * Set environment variables.
+  * Don't worry too much about minor bugs. We are looking
+     for blockers, such as it will not run. Many known issues
+     are recorded at our Jira, perhaps you can add more.
 
 * Make a fresh site ...
-cd my-new-dir
-forrest seed
-forrest run ... use the local jetty server.
-forrest ... build the whole site from the command-line.
-forrest war ... use your own full Jetty or Tomcat.
+    cd my-new-dir
+    forrest seed
+    forrest run ... use the local jetty server.
+    forrest ... build the whole site from the command-line.
+    forrest war ... use your own full Jetty or Tomcat.
 
 * Try it on the Forrest core docs ...
-cd site-author
-forrest run
+    cd site-author
+    forrest run
 
 * Forrest was already pre-built. Try building it again.
-cd main
-build clean
-build
-build test
+    cd main
+    build clean
+    build
+    build test
 
 * Try it on your own project, especially if you have
-a project sitemap and use some extra plugins.
+    a project sitemap and use some extra plugins.
 
 ------------------------------------------------------------------------------