[MO-java-dev] CVS: mockobjects-java/doc/xdocs release_process.xml,1.1,1.2

[Vincent M. <vm...@us...>]

Update of /cvsroot/mockobjects/mockobjects-java/doc/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv15795/doc/xdocs

Modified Files:
	release_process.xml 
Log Message:
- Updated the release process to use tasks defined in the SourceForge trackers
- Removed the reference to the features page which still does not exist. Users will have to "discover" the features from the changes.html file (completely empty since 0.01... :-(). Let's start to use it again please...

Index: release_process.xml
===================================================================
RCS file: /cvsroot/mockobjects/mockobjects-java/doc/xdocs/release_process.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- release_process.xml	21 Aug 2001 11:41:27 -0000	1.1
+++ release_process.xml	14 May 2003 14:57:58 -0000	1.2
@@ -29,10 +29,10 @@
       <p>
         Long before any release, we need to define what will go into that
         release, i.e. the list of tasks that need to be performed
-        <strong>prior</strong> to that release. These tasks will be listed on
-        the <link href="todo.html">Todo page</link>. Tasks can be proposed on
-        the <link href="http://sourceforge.net/mail/?group_id=18189">mailing
-        list</link>.
+        <strong>prior</strong> to that release. These tasks are listed
+        using the 
+        <a href="http://sourceforge.net/tracker/?group_id=18189">SourceForge 
+        trackers</a> ((bugs, requests, patches, RFE).
       </p>
 
     </s2>
@@ -87,17 +87,14 @@
         This is done by posting a mail on the list asking for a code freeze.
       </li>
       <li>
-        Verify that the <link href="todo.html">todo.xml</link> page is up to
-        date.
+        Verify that the no scheduled items from the
+        <a href="http://sourceforge.net/tracker/?group_id=18189">SourceForge
+        trackers</a> is still outstanding. If so decide whether to postpone 
+        the release or move the task to the next release.
       </li>
       <li>
         Verify that the <link href="changes.html">changes.xml</link> page is up
         to date.
-      </li>
-      <li>
-        Verify that the <link href="features.html">features.xml</link> page is
-        up to date and includes all features available in all releases + the
-        new ones from this release.
       </li>
       <li>
         Verify that the news items on the