Subject: Re: [boost] Getting Started with Modular Boost Library Maintenance
From: Beman Dawes (bdawes_at_[hidden])
Date: 2013-12-13 17:14:21
On Tue, Dec 10, 2013 at 1:29 PM, Vicente J. Botet Escriba <
> IMHO the Boost.System release shouldn't be correlated with Boost versions.
> E.g. Boost.Thread has version 4.2.0 and it appears on the documentation
Good point. I agree.
> For libraries that have not a version associated yet, they could start by
> the version they think it represents better the state of the library.
> Taking the history of the library should help to see on which version each
> library is (see http://www.boost.org/doc/libs/1_55_0/doc/html/thread/
> changes.html). I use to change the major version each time I introduce a
> breaking change, the minor version when I add more features and the patch
> when I just add fixes.
I'll suggest something like that as a numbering strategy.
... OK, done. See https://svn.boost.org/trac/boost/wiki/StartModWorkflow
> With Git, I guess the author should create a release branch, each time
> he/she consider it is time to do a release.
Whether or not a library maintainer uses a release branch is up to them,
but every time master is changed (i.e. pushed to) Boost will be potentially
treating it as a new release so it should have an updated release number.
(The exact details of that will evolve over time.)
> Of course this would mean that there is at least a version each time the
> library introduces changes on a official Boost release. This allows to take
> care of hot fixes independently of the other features the author is working
> on, which I think is something the Boost users are waiting for.
Yes, and easy point releases of my own libraries is certainly something I'm
looking forward to.