Le 25/06/2012 17:36, Richard Heck a écrit :
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 The only downside to this is that there will be more branches hanging around, but this doesn't seem like much of a cost, and it will make the 2.0.x branch cleaner. Thoughts?
That is fine with me. We could have done that with svn too, AFAIU. JMarc
