Re: [boost] Git: maintaining super-project

Subject: Re: [boost] Git: maintaining super-project
From: Philippe Vaucher (philippe.vaucher_at_[hidden])
Date: 2013-12-04 08:06:25

As said on irc I believe there are 3 main solutions to this problem:

   1. every library maintainer also has write access to the super repo and
   updates the super repo submodule references themselves.
   2. someone is responsible for updating the super repo (think linus for
   the linux kernel), and makes a bit of review before updating the submodule
   ref that changes
   3. automatic submodule update for the master/develop branches whenever
   something was pushed to master or develop in the submodule

Philippe

On Wed, Dec 4, 2013 at 7:00 AM, Vladimir Prus <vladimir_at_[hidden]>wrote:

>
> I am not sure how maintenance of subproject references in the
> super-project will work.
>
> - For 'master' branch, I assume that as developers update 'master' branch
> in their libraries,
>   they would submit pull requests, so that the super-project points at new
> commits. That shall
>   work, except that pull requests like this are hard to examine. E.g:
>
>         https://github.com/boostorg/boost/pull/4
>
>   If I did not specify direct links to commits, I don't know how anybody
> would decide whether
>   new revision is OK or not.
>
> - For 'develop' branch, I certainly don't think that for every change to
> 'develop' branch of
>   any library, there will be a pull request on superproject? Doing so
> would create a lot of
>   administrative overhead, and not doing that means that checking out
> 'develop' branch of
>   the superproject does not necessary pull heads of 'develop' branches of
> each library.
>
> Am I missing something?
>
> Thanks,
> Volodya
>
> --
> Vladimir Prus
> CodeSourcery / Mentor Graphics
> http://www.mentor.com/embedded-software/
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/
> mailman/listinfo.cgi/boost
>