Steve Langasek wrote: > 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?) I'm going to try to limit the changes to i386 in testing, so if I can force in an architecture dependant package to !i386, I will. If an architecture indep package must go in, it will also update i386 (but not the i386 CD images, which are already done). We will lose some consistency, but we're already going to be 90% more consistent than the last beta this way. > - When the music stops, those ports that have d-i candidates in testing > will be released as beta2. > > Is that right? Right on all counts. Note that sarge/main/debian-installer/binary-i386 currently has empty Packages files. They were fine yesterday but one of the girls ate them. I think that will be fixed tomorrow after ftpmaster finished getting their act together. -- see shy jo
Attachment:
signature.asc
Description: Digital signature