[GRASS-dev] GRASS 6.3.0

[Markus Neteler]

On Tue, Mar 18, 2008 at 1:52 AM, Glynn Clements
<glynn at gclements.plus.com> wrote:
>
>  Martin Landa wrote:
>
>  > >  There are a lot of other script fixes not backported to 6.3.0, mostly
>  > >  bulk quoting of variables. I didn't backport them as I have not
>  > >  individually tested the changes and so don't guarantee they are no
>  > >  introduced typos. These will help with the spaces in pathnames problems,
>  > >  which are mostly a MS Windows phenomenon. I did not systematically quote
>  > >  everything, so it is almost certain that there will be more unquoted path
>  > >  and file names. These fixes might be nice to get out to MS Windows users
>  > >  in a 6.3.1 after more testing in SVN/trunk. Probably easier to cut a new
>  > >  6_3_1 branch from the main grass6 line than to bother backporting things
>  > >  to 6.3.0's branch.
>  >
>  > Hm, creating branch for 6.3.1 seems to be a bit complicated to me. I
>  > would prefer releasing 6.3.0, creating branch for 6_4 (trunk for 7.x).
>  > Releasebranch_6_3 used for 6.3.1 (after tagging 6.3.0) as usually.
>
>  I would suggest keeping with releasebranch_6_3 for 6.3.1 (if it
>  occurs).

I agree. That's the most cost effective way.

>  If you were planning on a release which (roughly) corresponds to the
>  current trunk, that should probably be 6.4.0. The differences between
>  6.3.1 should consist only of changes which have been vetted and deemed
>  necessary.

This corresponds to the graph in
http://trac.osgeo.org/grass/wiki/Grass7Planning

Proposal

End of this month:
* Get out 6.3.0final (releasebranch_6_3)
* Immediately branch off 6.4.0 to releasebranch_6_4
* rename trunk to 7.0.svn

Markus