Boost logo

Boost :

Subject: [boost] [git] automated update of superproject master branch
From: Peter A. Bigot (pab_at_[hidden])
Date: 2013-12-27 11:21:41

I realize there are several email threads about how the super-project
branch should be managed, but most pre-date live experience with boost
on git and go deep into other aspects of the issue, so I still want to
call this out specially: specifies that the
master branch on each module should be stable at all times, which is the
right policy.

Currently, the master branch on the super-project is automatically
updated twice(?) per hour selecting all updates to the master branches
of modules. Consequently, super-project master is the exact opposite of

This divergence is confusing. I'm unconvinced that waiting a few days
will demonstrate a significant decrease in churn on the super-project
master branch. Some is due to multiple updates to specific modules,
which might decrease as maintainers become more familiar with git and
only push once, but interoperability issues will still arise and there
will be no way to tell which master branch commits produce a working
Boost installation.

There is value in having a branch with automated-update semantics, but
IMO regardless of what the final policy will be, "master" is not the
right choice for this, and automated updates of it should stop ASAP.
Perhaps the update script can simply be moved to occur on latest/master
and latest/develop. Leave master untouched until whatever gets
committed to it has undergone cross-toolchain integration validation,
and make develop available for changes to superproject content that are
not just submodule updates.


Boost list run by bdawes at, gregod at, cpdaniel at, john at