Subject: Re: [boost] [git help] Documenting common modular boost workflows
From: Daryle Walker (darylew_at_[hidden])
Date: 2013-10-21 14:57:05
Since a project thatâs made of a bunch of sub-repositories thatâs later merged is (AFAIK) unusual, I donât think the writer of gitflow had it in mind.
Iâm guessing that each sub-repository independently uses gitflow. When itâs shipping time, the release-merge script grabs from the âmasterâ branch of each sub-repository. Of course, this doesnât cover multiple libraries that have to work together or what happens when fixing is necessary (probably due to cross-library problems).
And do the test runners work off âdevelop,â âmaster,â ârelease,â or does it shift depending where we are in the release cycle?
Sent from Windows Mail
From: Peter Dimov
Sent: âMondayâ, âOctoberâ â21â, â2013 â10â:â16â âAM
To: Boost Dev-List
Dave Abrahams wrote:
> IIUC we already agreed long ago to use gitflow:
It's not entirely clear to me what using gitflow would mean in the context
of a Boost superproject with per-library submodules. Who is "we" who would
be using gitflow, the Boost release managers or the library maintainers?
When Boost release 1.64.0 is started, who is going to create the gitflow
release branch, and from what?
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk