On Wed, 2010-03-03 at 17:32 -0500, Chris Lumens wrote: > > 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. > > Okay, a refinement of my point but with references to the F-13 schedule > to make this more concrete: Oops. We haven't updated the schedule dates for NFR yet, so let me try and adjust on the fly here. > > 2010-02-09 - Feature Freeze/Branch F13 from rawhide > At this point, we create an f13-branch off master, and > an f13-alpha-branch off that one. Bugs marked as > F13Alpha get committed here, builds for Fedora 13 come > from here. Stuff that needs to go in for F13 but is > not alpha worthy goes onto f13-branch. New development > and all other bug fixes continue on master. We don't actually branch dist-cvs at feature freeze. We would do that a week later at the 'Branch Freeze' point. So while you could create your f13-branch here, you don't necessarily need to create the f13-alpha-branch. > > 2010-02-16 - Alpha Freeze Make this say Branch Freeze > Create an f13-beta-branch. The only things that get > committed to f13-alpha-branch are blockers found in testing > candidate trees. F13Beta blockers get committed to > f13-beta-branch. Builds for Fedora 13 come from > f13-alpha-branch. Stuff that needs to go in for F13 but is > not beta worthy goes onto f13-branch. New development and all > other bug fixes continue on master. I'm very confused here. Why would you create the f13-beta-branch at this point? All that should be necessary are the f13-branch and f13-alpha-branch. Stuff for 13 goes to f13-branch. Stuff for alpha gets cherrypicked onto f13-alpha-branch. New development and whatnot goes onto master. > > 2010-03-02 - Alpha Release > f13-alpha-branch is dead. Makes sense. Builds come from f13-branch. > > 2010-03-23 - Beta Freeze > Create an f13-rc-branch. The only things that get committed > to f13-beta-branch are blockers found in testing candidate > trees. There shouldn't be any bugs that are important but > can be put off from beta to RC. However if there are, > those get committed to f13-rc-branch. Builds for Fedora 13 > come from f13-beta-branch. New development and all other > bug fixes continue on master. So again, I think you're creating the next branch point too early. When we get to beta freeze (which doesn't really exist anymore), that's when you'd create the f13-beta-branch, and do your cherry picking and building from there. > > 2010-04-06 - Beta Release > f13-beta-branch is dead. With you again, builds now from f13-branch once more. > > 2010-04-29 - Compose Release Candidate > Up to somewhere around this date, blockers continue getting > committed to f13-rc-branch, and builds for Fedora 13 come > from this branch. Very little activity at all should be > happening here. This is the point in which the f13-rc-branch should get created, and gated. Either that or you gate f13-branch entirely, since we're no longer doing anything future looking in 13, what's in is in, unless it's broken and we have to fix it. All else goes to master, f13-branch (and f13-rc-branch if you choose to make one) are heavily guarded and selectively committed to. > > 2010-05-11 - Fedora 13 Final Release > f13-rc-branch is dead. f13-branch should reflect what was > released, and may continue on to be used by Fedora Unity > or similar purposes. Makes sense here. -- 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
