Re: [Gramps-devel] 3.2 in roadmap?

[Brian M. <br...@gr...>]

Gary,

> >The way some projects do it is that they tag alpha,
> beta, then a first release candidate from trunk, so
> >trunk remains the code that will become 3.1.0. Like
> that people are forced a bit to work further on
> >the release candidate.
> 
> >Then when the second/third release candidate is made,
> gramps31 is made from trunk, and trunk is
> >open for future 3.2 
> >So it just comes down to doing the split of the branch
> not too early.
> 
> I always assume that the decision point when to split off a
> branch is determined when the code for the next release
> becomes feature complete in trunk and this usually happens
> when it's time for a beta release. Bug fixing carries on
> for as long as necessary in the branch whilst tagging
> occasional release candidates. If a release candidate
> appears stable enough then it's also tagged as the first
> release.

You are right. This is the process we used for 3.0 and it worked great. I recommend that we do it this way for 3.1. when all the features are complete in trunk, we tag the 3.1 maintenance branch. We should probably do this by mid-February so that we have time to fix bugs.

> That's how I've always worked - never release from
> trunk and so trunk is only frozen for the time it takes to
> split a branch. :)

Since commits are atomic in Subversion, this is instantaneous :)

~Brian