[GRASS-PSC] too many branches

[Yann Chemin]

In favour of giving the devbranch6 a prune, I cannot remember when I used
grass6-dev last time...

+1 to remove devbranch6 after appropriate transfer of the needed to
releasebranch6.

Do we have a tentative time line to freeze Grass6 release branch (1 year?)


Yann


On 29 March 2014 11:34, Luca Delucchi <lucadeluge at gmail.com> wrote:

> Hi PSC,
>
> with the upcoming GRASS 7 release we have to many branches to maintain
> (releasebranch6, devbranch6, releasebranch7 and trunk).
> Can I ask you to take a decision about the future of all this branches?
>
> I could suggest something like:
> - keep releasebranch6 only for important bugfixes, no new feature and
> starting to forget it
> - put in reading mode or remove (after backport the differences with
> grass64) devbranch6
> - releasebranch7 is the new stable release branch, so new features
> only when we are far from release a new version
> - trunk for new feature
>
> what do you think?
>
> Thanks a lot
> Best regards
>
> --
> ciao
> Luca
>
> http://gis.cri.fmach.it/delucchi/
> www.lucadelu.org
> _______________________________________________
> grass-psc mailing list
> grass-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-psc
>



-- 
----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20140331/63a0ff9c/attachment.html>