* Otavio Salvador <ota...@debian.org> [2009-11-23 19:44]: > Currently installer itself is more or less in a good shape however we > have two bugs that are blockers for this release. They are: > > #557387 - Graphical installer is brokeness (cjwatson and/or lunar) > #556635 - udev: blanks inserted RW media (fixed in GIT already)
Is g-i really a blocker for alpha1? I'd much prefer the fixed udev to be uploaded and an alpha1 release made now without g-i, followed by an alpha 2 that updates the kernel to 2.6.31 and adds g-i. > Since we have a window until the graphical installer and udev issues are > solved I'm thinking about we move to 2.6.31 in d-i. I see following pros > in doing it: ... > The plan is to start working locally in the transition and if udev > and/or gtk+ is not ready when kernel is done then we start moving to new > kernel otherwise we go with 2.6.30 as is now. I'm not convinced that going to 2.6.31 now is such a good idea (since it always takes forever to get all arches updated), but since we have good 2.6.30 udebs in testing I guess putting 2.6.31 into unstable might not be such a big deal. In any case, 2.6.31 works fine on ARM and I can update 2.6.31 on ARM and MIPS quickly if we decide to go this way. Actually, 2.6.31 (-1 and -2) failed to build on powerpc (*sigh*), so going to 2.6.31 might not be an option anyway... Or can we keep the 2.6.30 udebs on powerpc and update all other architectures to 2.6.31? > 21 Dec 2009: release So we're over 6 months late. This is really frustrating. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
