Subject: Re: [Boost-build] Merging trunk tools/build changes to branches/release
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2009-01-15 22:11:27
Beman Dawes wrote:
> We need to establish the responsibility for merging trunk tools/build
> changes to branches/release. Six different people made tools/build
> changes since 1.37.0, yet there were no merges to branches/release.
> I guess that means everyone thinks merges to branches/release are
> someone else's responsibility.
> As a release manager, I don't care who does the merges. But it does need
> to be someone who is familiar with what's going on in the Boost.Build
> world, so that what to merge and when to merge gets chosen appropriately.
For BBv1 the responsibility was mine. But for BBv2 it's been Volodya's
task. It's unfortunate that he was occupied right at key merge time this
time around. But eventually we have to resolve the issue of doing
"stable" BBv2 releases that can then be merged consistently to Boost. In
the same way I do the bjam releases and merges.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk