Subject: Re: [boost] Release managers: Boost.Thread breaking changes in 1.53
From: Daniel James (dnljms_at_[hidden])
Date: 2012-12-31 08:51:25
On 31 December 2012 07:44, Roland Bock <rbock_at_[hidden]> wrote:
>
> Since more than 50 releases there has been one minor release number
> change (1.x -> 1.(x+1)) after the other. No distinction.
That's not actually true. See:
http://www.boost.org/users/history/
e.g. 1.46.1, 1.34.1, 1.33.1. They've happened less often since we
adopted a regular release schedule.
> Maybe this can be achieved with distributed boost?
Distributed is largely irrelevant here, unless there are volunteers to
maintain a stable fork? Improved branching could help, but the idea
seems to be that modularization will change the way releases are
handled.