On Aug 30, 2011, at 2:45 PM, Martin Landa wrote:
> 2011/8/30 Michael Barton <[email protected]>: >> Seems an even stronger reason to focus limited development efforts on a >> single branch. > > that's what we are more or less doing (see who commits to trunk). > Anyway there is still need of fixing bugs in GRASS 6.4, improving > winGRASS, preparing new release, etc. I'm completely in agreement. We should move ahead with a release cycle for 6.4.2 and get this done with. > What I don't understand are > never-ending discussions about what we cannot do in GRASS 6.x branches > instead of discussing what should be done in GRASS 7 (including > someone who will implement ideas) and motivation people to maintain > GRASS 6.4 for next release (since GRASS 7 release is in the stars). I guess my suggestion would be to work on fixing bugs and finishing things in progress on GRASS 7 before adding anything else new. This is not recommending a feature freeze, but simply to get a better idea of where we are with GRASS 7. A clear roadmap would be helpful of course. Michael > > Martin > > -- > Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
