Re: [boost] Git: maintaining super-project

Subject: Re: [boost] Git: maintaining super-project
From: Vladimir Prus (ghost_at_[hidden])
Date: 2013-12-04 01:28:05

On 04.12.2013 10:14, Andrey Semashev wrote:
> On Wed, Dec 4, 2013 at 10: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?
>
> As far as I understand, you don't have to create pull requests for
> master and develop branches. The actual revision is pulled from
> submodules automatically as you check out the monolithic boost (the
> boostorg superproject). The pull requests might be needed during the
> release cycle, if you want specific last minute changes pulled by the
> release managers so that they get into release.

Well, the superproject has references to specific revisions of each component. Or am I mistaken
on this part?

- Volodya