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.
If we go that route then we already have the beta for 1.58.1: it's called 1.58.0. So we could allow low risk bugfixes for a limited time, and then go straight to a release candidate.
I'm not sure I understand that. But one thing we could do is leave the beta out there for testing longer. Right now we put it out there and ask people to try to install it and test it. I understand how they install it, but I'm not sure how they test it. We don't have a widely used/promoted procedure for testing one's release on one's own machine (do we?). Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/1-58-1-bugfix-release-necessary-tp4674686... Sent from the Boost - Dev mailing list archive at Nabble.com.