Subject: Re: [boost] Boost.Build merge?
From: Eric Niebler (eric_at_[hidden])
Date: 2008-10-10 17:15:42
Vladimir Prus wrote:
> I would have like to merge Boost.Build state from trunk to release branch.
> This matter was discussed briefly in
> but it didi not lead anywhere, and further it seems to be some confusion
> between merging Boost.Jam (which Rene wants) and merging Boost.Build.
> To reiterate, I think Boost.Build should be merged because:
> - it now supports linux->windows cross compile
> - it allows to eliminate configuration warning messages from
> libraries that are not built (which requires corresponding
> merges for libraries Jamfiles, but it's trivial)
> - it fixes a bug where include=/foo/bar could not be specified
> on the command line
> - it has some other smaller fixes
> - I don't see any breakage on trunk tests
The development process should work like this: you make a change to
trunk, wait for tests to cycle, and if they look good, you merge the
change to release. The process should *not* work like this: you make
change after change to trunk, and wait until the very last minute to
drop them all into the release branch at once.
Some of these improvements are desirable, though. Can you send links to
the changesets you'll be merging? And describe potential impacts?
-- Eric Niebler BoostPro Computing http://www.boostpro.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk