Hello, On Fri, Jan 11, 2008 at 11:46:11AM -0700, dann frazier wrote: > * Go with 2.6.22 for now - its more stable than 2.6.23 and is a known > quantity. I could get a branch going and start on any security > fixes, and upload sometime soon, perhaps Wednesday? OK > * Encourage users to test 2.6.24 rc releases - maks wants to make rcs > available in experimental, and try for a quick upload to sid once > upstream releases. Yes, we should aim at .24. > * 4.0r3 is intended to happen in February, and mainly to fix issues > with 4.0r2 - 4.0r4 would be the next candidate for etchnahalf. That should be possible, with .24 > * Revisit the 2.6.22 decision once 2.6.24 has been in sid for 2 > weeks. If 4.0r4 is still far enough out (e.g., if 4.0r3 hasn't > happened by this point), and no major issues have been uncovered so > far, it seems reasonable to switch. Sounds like a good plan =) Best regards Frederik Schüler -- ENOSIG
Attachment:
signature.asc
Description: Digital signature