[GRASSweb-list]markus: web codemanagement.html,1.10,1.11

[grass at intevation.de]

Author: markus

Update of /grassrepository/web
In directory doto:/tmp/cvs-serv27506

Modified Files:
	codemanagement.html 
Log Message:
updates as identified by Hamish Bowman

Index: codemanagement.html
===================================================================
RCS file: /grassrepository/web/codemanagement.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- codemanagement.html	27 Nov 2002 09:05:08 -0000	1.10
+++ codemanagement.html	4 Dec 2002 09:08:34 -0000	1.11
@@ -12,8 +12,7 @@
 <h1>
 GRASS CVS and release strategies</h1>
 <b>The symptoms:</b>
-<br>We do not release tarballs frequently enough. The long needed 5.0 stable
-release has not happened yet.
+<br>We do not release tarballs frequently enough.
 <p>Our goal is to release something better than the last release but we
 are not able to write perfect system at this moment. Stable release may
 be any release which has all functionality which was stable and common
@@ -113,29 +112,29 @@
 <li>
 Markus will only release source tarball.</li>
 
-<li>
-The tarballs will announced to helpers and alphatesters one week in advance
-so there is a change to build binaries. If binaries will not be produced
-the release will be announced anyway.</li>
+<li> The tarballs will be made available to alphatesters one
+week in advance along with selected binaries. If no binaries will
+be produced immediately the release will be announced anyway.</li>
 
 <li>
-There will be a scripts so that binaries can be build automatically.</li>
+There is a script to build binaries automatically. This can be distributed
+on demand to enable more people to build standard binaries for the various
+platforms.</li>
 </ol>
+
 It is necessary to give a time frame and stick to it. If not enough people
-can be found to test "pre" releases or create binaries in time, we have
-to consider that there is less interest in the functionality in question
-or the ports. Generally it is not in the resonsibility of Markus to make
-sure
-<br>that we support all available combinations of hardware and software.
-<br>&nbsp;
+can be found to test "pre" releases or create binaries in time, we have to
+consider that there is less interest in the functionality in question or the
+ports. Generally it is not in the resonsibility of the GRASS Development
+Team to make sure that all available combinations of hardware and software
+are supported.
+
 <p><b>Next steps</b>
 <p>The webpages of GRASS are managed in the CVS. There is a script in place
-which will update them once a day or triggered by Markus. Any developer
-with CVS write access can directly help with the webpages now.
-<p>Markus plans to have another 5.0.0pre4 release which will follow the
-strategy outlined above. There will be at least one release branch and
-a 5.0.0pre5 before the 5.0.0 release. Pre5 has to be aimed for as fast
-as possible.
+which updates them several times a day or triggered by Markus. Any developer
+with CVS write access can directly help with the <a
+href="grasscvs.html#web">webpages</a> now.
+
 <p><b><font color="#FF0000">Please identify the release critical bugs.</font></b>
 <p>
 <hr WIDTH="100%"><a NAME="Addendum"></a><b>Addendum</b>