On Mon, May 10, 2010 at 06:23:27PM +0530, Rahul Sundaram wrote: > On 05/10/2010 05:47 PM, Adam Williamson wrote: > > > There's definitely not been a blocker bug for it, but thinking about it, > > I can confirm the problem - when I installed F13 on this machine it had > > Windows XP on it, and F13 correctly set up a bootloader config with an > > entry for loading XP, but set the timeout to 0 :/. I just never really > > thought about it and realized it was something we really ought to fix > > for final. > > > > At this point we're _probably_ just going to be documenting it, I'm > > afraid. If not, we certainly have to slip the release a week. If you'd > > like to argue for the slip to fix this bug, or at least have it formally > > discussed, please file a bug on this - specifically on the multiboot > > case, if you open it just against the overall default to 0 it'll > > probably get closed quite fast :) - and mark it as blocking F13Blocker. > > > > https://bugzilla.redhat.com/show_bug.cgi?id=590661 > > Marked as blocker. https://fedorahosted.org/fesco/ticket/377 FESCo is considering whether this is blocker-worthy on its own. I weighed in, and regardless of the decision I'm happy it's being looked at thoughtfully. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ Where open source multiplies: http://opensource.com -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
