[GRASS-dev] GRASS 7 release planning

[Moritz Lennert]

On 20/06/14 21:17, Markus Neteler wrote:
> Hi devs,
>
> ... so, getting out 7.0 seems to be endless...
>
> A radical solution might be to change trunk into GRASS GIS 8. Then we
> do not need to wait in 7 for API stabilization and can release it "as
> is" and go ahead with the planned massive improvements.

This sound ok to me. So, ideally, at all times we should have one 
release branch and one development branch. Releases can then just be 
tagged from the release branch which gets only selected, well-tested, 
not to invasive backports from the dev branch.

Once we decide that the dev branch is sufficiently different from 
release that backports become unfeasible, and sufficiently stabilised 
that we can branch a release branch out of it, we declare the previous 
release branch a legacy maintenance branch (with only limited bug fixing 
from that point on), and branch a new release branch.

The proposed RFC4 release procedure would then apply to the release branch.

I think this will help reduce the number of branches which currently is 
a hassle.

But, even though, I know you are in a hurry to get a grass7 release out 
of the door, don't you think that we should finish 6.4.4 first ?

To be honest I think we will have to accept shipping OSGEOLive with 6.4.4...

Moritz