Re: [boost] 1.35 release approach (was [1.34.0] Deadline)

Jeff Garland wrote:

Actually, I think Beman's new approach is much closer in philosophy to what I'm suggesting. As I recall in provides for a small window to fix regressions after which breaking changes will be reverted. It's ultimate goal is to keep the HEAD much closer to release at all times. Still, it is untested so we don't know how it will really work yet.

As I understand it, "keep HEAD release-ready" is the opposite of what you are suggesting, which is "branch 1.35 as soon as 1.34 is released". In fact, there is no need to wait for 1.34 to be released - you can have the 1.35 branch proceeding in parallel (general lack of resources aside.)