[git] automated update of superproject master branch
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: https://svn.boost.org/trac/boost/wiki/ModBigPicture 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 stable. 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. Peter
On Fri, Dec 27, 2013 at 11:21 AM, Peter A. Bigot
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:
https://svn.boost.org/trac/boost/wiki/ModBigPicture 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 stable.
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.
Several release managers exchanged emails about this earlier today, and the consensus was to start a discussion on the list based on the Dimov proposal. But that discussion hasn't started yet and the earliest any actual change can be made is sometime next week. Remember, we are all unpaid volunteers. Thanks, --Beman
On 12/27/2013 10:38 AM, Beman Dawes wrote:
Several release managers exchanged emails about this earlier today, and the consensus was to start a discussion on the list based on the Dimov proposal. But that discussion hasn't started yet and the earliest any actual change can be made is sometime next week. Remember, we are all unpaid volunteers.
Understood. I wanted to make sure it was going to be addressed as soon as possible; the world won't come to an end if that's next week. Peter
----------------------------------------
Date: Fri, 27 Dec 2013 10:46:23 -0600 From: pab@pabigot.com To: boost@lists.boost.org Subject: Re: [boost] [git] automated update of superproject master branch
On 12/27/2013 10:38 AM, Beman Dawes wrote:
Several release managers exchanged emails about this earlier today, and the consensus was to start a discussion on the list based on the Dimov proposal. But that discussion hasn't started yet and the earliest any actual change can be made is sometime next week. Remember, we are all unpaid volunteers.
Understood. I wanted to make sure it was going to be addressed as soon as possible; the world won't come to an end if that's next week.
Just curious whatever happened to this? https://svn.boost.org/trac/boost/wiki/SuperProjectWorkflow It doesn't seem to be implemented yet, is it still in planning stages?
On 14 February 2014 10:07, Ahmed Charles
----------------------------------------
Date: Fri, 27 Dec 2013 10:46:23 -0600 From: pab@pabigot.com To: boost@lists.boost.org Subject: Re: [boost] [git] automated update of superproject master branch
On 12/27/2013 10:38 AM, Beman Dawes wrote:
Several release managers exchanged emails about this earlier today, and the consensus was to start a discussion on the list based on the Dimov proposal. But that discussion hasn't started yet and the earliest any actual change can be made is sometime next week. Remember, we are all unpaid volunteers.
Understood. I wanted to make sure it was going to be addressed as soon as possible; the world won't come to an end if that's next week.
Just curious whatever happened to this?
https://svn.boost.org/trac/boost/wiki/SuperProjectWorkflow
It doesn't seem to be implemented yet, is it still in planning stages?
I think people have been occupied with other things. If everyone's okay with it, I could do it after the regression tests have been modularized.
participants (4)
-
Ahmed Charles -
Beman Dawes -
Daniel James -
Peter A. Bigot