On Wed, 2010-03-03 at 13:44 -0500, Chris Lumens wrote: > What we'll have here is that f13-branch will be sort of like a master > branch for all things F13 related but no builds will ever come from it - > all builds will come from one of the alpha/beta/rc sub-branches. > > That means if anyone can commit anything to f13-branch, they have no > guarantee that it will ever make it into a build. A commit will only > make it into a build if the release manager pulls it onto the > appropriate sub-branch. Is everyone okay with that lack-of-guarantee? > I'm not sure how I feel about it. > > I guess one serious advantage to it is that the release manager has a > smaller pool of candidate commits to sift through looking for things to > cherry-pick. Letting people commit to f13-branch means there's a bit of > a filter at the developer's level first. Only doing builds from a -alpha/-beta/-rc branch only seems to make sense once releng makes an release candidate for alpha/beta/final. In between those times, the builds should come from the 13 branch. The only exception to this I think would be the final stage, where there is nothing after that compose. At that point, changes to the 13-branch should be limited as well, since there wouldn't be any later build to pick up those changes. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
