Andres Salomon wrote: > I'm of the opinion that if sarge is literally less than a month away from > freezing, then let's stick w/ 2.6.8. It's Good Enough; if we can get > around ACPI problems by disabling it, fine. However, if sarge is still > far away from freezing, then there's no reason not to go w/ 2.6.10. > It's clearly shown itself to be a better kernel in some cases; we just > need testing to find regressions in *core* stuff (individual drivers, > filesystems, etc, can all have fixes backported. It's the core stuff > that's difficult). I'm not concerned about when d-i rc3 is released; I > care about when *sarge* releases. People said that once rc2 was out, sarge > would be ready. That's clearly not the case, and probably won't be the > case once rc3 is out. a) The last thing I want to do is place d-i in the position of being the last thing blocking the sarge release, and swapping out the kernel at this point has a very good potential to do so. I think vorlon agrees, but I'll stop quoting his offhand comments on irc now. :-) I'm rather happy actually that you think we can release with 2.6.8. b) Many of the people whose time would be spent working on updating d-i to a new kernel could better use that time to work on other RC issues for sarge. For example, I work on tracking security issues in testing. Kamion and vorlon work on getting the release out. Etc. -- see shy jo
Attachment:
signature.asc
Description: Digital signature