Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Forrest Developers List" <dev@forrest.apache.org>
Message-ID: <20050613140352.18330.qmail@minotaur.apache.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: svn commit: r190406 - /forrest/trunk/etc/RELEASE_PROCESS.txt
Date: Mon, 13 Jun 2005 14:03:52 -0000
To: svn@forrest.apache.org
From: crossley@apache.org

Author: crossley
Date: Mon Jun 13 07:03:51 2005
New Revision: 190406

URL: http://svn.apache.org/viewcvs?rev=3D190406&view=3Drev
Log:
Fix last commit, wrong email template.

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?re=
v=3D190406&r1=3D190405&r2=3D190406&view=3Ddiff
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- forrest/trunk/etc/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/etc/RELEASE_PROCESS.txt Mon Jun 13 07:03:51 2005
@@ -285,63 +285,39 @@
    http://www.mail-archive.com/dev@forrest.apache.org/msg02310.html
=20
 --------------------------------------------------------------------------=
----
-Subject: [Important] please test release candidate then vote
+Subject: [Important] code-freeze commenced
=20
-We need people to test the release candidate on your projects,
-especially on different operating systems. Just send a short
-reply to this thread that it works for you. See method below.
-
-Download the release candidate and supporting files:
-http://www.apache.org/~crossley/release-forrest-07/
-
-For Windows get *.zip md5sum ################################
-For UNIX get *.tar.gz md5sum ################################
-Get the *.asc and *.md5 that match your chosen download.
-
-It was packed from SVN revision ####
-Java 1.4 or later is required.
-
-If you want to verify the download, then follow:
-http://forrest.apache.org/mirrors.cgi#verify
-
-Otherwise just get on with testing.
-
-Testing and vote period concludes Sunday 2005-06-19 14:00 UTC
-Anyone can test and vote, not just PMC members.
-However only the PMC votes are binding.
-
-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.
-
-* 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.
-
-* Try it on the Forrest core docs ...
-    cd site-author
-    forrest run
-
-* Forrest was already pre-built. Try building it again.
-    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.
+The code-freeze is now happening to allow us to pack the
+release candidates and make them available for testing.
=20
+Code-freeze means *no* non-essential commits to the trunk
+or to the new release branch. Other branches are free to
+continue.
+
+There should be no code enhancements or new functionality,
+because that could introduce new bugs.
+
+The main aim is to find and fix important bugs. Any minor
+issues are delayed until after release (add to Jira).
+
+Documentation corrections can happen because they will not
+break anything. As long as we do test the documentation
+building just prior to making the final release candidate.
+
+However, if there are important code changes that are required
+you can make a proposal to allow that commit. The PMC will
+make a quick decision.
+
+Next important milestones are:
+* Create release candidate #2 if there have been changes
+on Friday 2005-06-17 at 22:00 UTC [2]
+[2] http://www.timeanddate.com/worldclock/meetingtime.html?day=3D18&month=
=3D06&year=3D2005&p1=3D48&p2=3D176&p3=3D240&p4=3D224&p5=3D213
+* Actual release date is Sunday 2005-06-19 at 14:00 UTC [3]
+[3] http://www.timeanddate.com/worldclock/meetingtime.html?day=3D20&month=
=3D06&year=3D2005&p1=3D48&p2=3D176&p3=3D240&p4=3D224&p5=3D213
+
+Now we will go and build the releases which might take
+some time. The next message will tell you where to get
+the release candidates and describe how to test.
=20
 --------------------------------------------------------------------------=
----
 Subject: [Important] please test release candidate then vote