On 04/26/2015 10:58 AM, Robert Ramey wrote:
John Maddock-2 wrote
On 26/04/2015 14:38, Robert Ramey wrote:
What is would be the difference between creating a bug fix release presumably called 1.58.1 and just expediting release 1.59 ?
A bugfix release is exactly that - bug fixes only, no new features or new libraries.
If we do that, then we'll have to create a new branch since there's already new stuff in master. Now we'll have to retest the "bug fix" release. And, we'll have to make sure that all the bug fixes get merged back into the master from from which the next release is going to be derived.
Seems to me a lot of work when the same effort could be applied to the next release.
This is how "git flow" works. It isn't a lot of work and it greatly reduces risk. While we let authors control their repositories mostly in whichever manner they wish, it would be prudent to follow the branching model here http://nvie.com/posts/a-successful-git-branching-model/. Unless the author already has substantial and practical experience with Git, using a well-tested work flow is going to be the best pattern for success. michael -- Michael Caisse ciere consulting ciere.com