On Mon, Jan 05, 2004 at 08:01:43PM -0500, Joey Hess wrote: > Petter Reinholdtsen wrote: > > > > [Joey Hess] > > > The branch is set up, it's called "beta2", so "cvs update -r beta2" to > > > switch a tree over to it, etc. So this means that cvs head is open for > > > random development not targeted at beta 2. > > > > Do we upload from the branch or from the trunk? > If it's random development not targeted at beta 2, to the trunk. So to recap and make sure I understand this correctly: - Normal development takes place on the trunk. - Changes required for beta2 (presumably for one of the ports) are made on the branch as well. - Uploads to unstable of d-i packages should come from the beta2 branch only. - When a port is considered a viable beta candidate, it will be frozen into testing along with i386. (Will i386 also get a pulse from unstable at this time, or will we lose the ability to rebuild all of testing from source during this freeze?) - When the music stops, those ports that have d-i candidates in testing will be released as beta2. Is that right? -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature