You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2007/04/03 02:17:03 UTC
svn commit: r524980 - in /forrest/trunk: etc/README.txt
etc/RELEASE_PROCESS.txt
site-author/content/xdocs/procedures/release/How_to_release.xml
Author: crossley
Date: Mon Apr 2 17:17:02 2007
New Revision: 524980
URL: http://svn.apache.org/viewvc?view=rev&rev=524980
Log:
Remove etc/RELEASE_PROCESS.txt as it is now incorporated into How_to_release.xml
Removed:
forrest/trunk/etc/RELEASE_PROCESS.txt
Modified:
forrest/trunk/etc/README.txt
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
Modified: forrest/trunk/etc/README.txt
URL: http://svn.apache.org/viewvc/forrest/trunk/etc/README.txt?view=diff&rev=524980&r1=524979&r2=524980
==============================================================================
--- forrest/trunk/etc/README.txt (original)
+++ forrest/trunk/etc/README.txt Mon Apr 2 17:17:02 2007
@@ -2,4 +2,3 @@
RELEASE-NOTES*: Release notes for various Forrest versions
build.number: File automatically generated by build.xml.
-RELEASE_PROCESS.txt: Describes how to make a Forrest release.
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?view=diff&rev=524980&r1=524979&r2=524980
==============================================================================
--- 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 Mon Apr 2 17:17:02 2007
@@ -62,8 +62,8 @@
<section id="About">
<title>About this document</title>
<warning>
-This document is still being developed from etc/RELEASE_PROCESS.txt and
-some steps will need to be re-arranged.
+This document is still being developed and
+some steps might need to be re-arranged.
</warning>
<p>This documents the steps that the Release Manager (RM) should follow when doing a Forrest release. Note
that it might have mistakes - we seem to discover something new each time and some steps might need to