Re: [boost] Git: maintaining super-project

Subject: Re: [boost] Git: maintaining super-project
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-12-04 02:39:35

On Wed, Dec 4, 2013 at 11:27 AM, Cox, Michael <mhcox_at_[hidden]> wrote:
> On Tue, Dec 3, 2013 at 11:35 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
>
> Now I'm not sure that's what you need.  You will get the latest changes
> from each of the repositories, but what are the entrance criteria for
> adding something to develop or master?  Does it have to compile?  Do all
> the changes have unit-tests that pass?
>
> I would assume the criteria for master would be more strict that develop,
> e.g. all changes on develop for a repository have to build with the latest
> changes on all the other repositories while changes on master have to also
> pass all their unit-tests.

Given that git develop == svn trunk and git master == svn
branches/release, I expect the criteria to be the same as with svn.
The essential point is that both develop and master should be checked
out at the latest revision by default, so that the actual code is
tested and released. The updates to the latest revision should happen
transparently, without requiring library maintainers to issue pull
requests or anything.