From: Beman Dawes (bdawes_at_[hidden])
Date: 2007-11-05 16:49:38
Joel de Guzman wrote:
> Beman Dawes wrote:
>> I think the procedure for such breaking changes should be something like:
>> * Create a branch, branches/system. The contents are the entire
>> boost tree.
>> * Apply the Boost.System changes to that branch.
>> * Announce the branch on the list, and encourage any developers
>> affected to update their libraries on the branch.
>> * Once all affected libraries are changed on the branch and
>> passing tests on developer's machines, merge the changes into
>> a working copy of the trunk and do a single commit.
>> * Watch regression tests closely to be sure nothing else broke.
>> Does this sound right?
> I'd add:
> * Try to fix all affected dependent boost libraries, if possible.
> * Announce the branch on the list, and encourage any developers
> affected to update their libraries on the branch.
Yep, that makes sense.
> This is how I did it with the recent fusion tweaks. I also recall that
> the MPL author(s) also graciously tweaked all dependent libraries
> when they changed apply_if to eval_if.
I'm under the impression Chris may maintain asio files elsewhere, so
asio may be a special case. Chris?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk