Richard Heck wrote: > With git, it no longer seems necessary to close branch to do a release. I > propose in future to do the following, starting with 2.0.5: > > 1. At release time, create a 2.0.5 branch, where any additional work that > might need to be done can be done. > 2. Change configure.ac to 2.0.6dev, so work can continue there > 3. When I actually release 2.0.5, create a tag on that branch
I think that the scenario for 2.0.5.1 happens once upon year or two, so my suggestion would be to normally tag the release and branch 2.0.5(.x) only in the sparse emergency case. Pavel
