Kernel Releases
Quoted 9 lines · Mike Galbraith
Quoted 7 lines
Quoted 2 lines
The only way we can get good testing for new kernels is to stop using -preN prefix in development branch (2.5.x). Just increment that 'x'.
That won't change anything except the number on the kernel. The people who you're trying to turn into bleeding edge testers (those who stay a little behind [bignum]) will continue to ride the curve at the point of their choosing.
Quoted 5 lines
Yes, but they can't tell which 2.5.x is more stable just from version number. This way Linus will get better test coverage in 2.5.x.
Those who need stability can read lkml and figure out which 2.5.x was 'glitchless' :-) or stick with 2.4.x
Agreed. 2.5.x should not use -pre. Just increment X.
2.4.x should continue to use -preY.
There's no need for a -rcY as some have suggested. All we need to do to avoid messes like the 2.4.15 debacle is to insist that a 2.4.X-preY should not be released as final 2.4.X until the pre's been out for a week, and there should never be any changes introduced into a final that didn't cook for a week as a pre. Marcello, what say ye?
That should give enough time for everyone to
find bugs and yell.
- Dan
Quoted 7 lines · Dan Kegel
2.4.x should continue to use -preY.
There's no need for a -rcY as some have suggested. All we need to do to avoid messes like the 2.4.15 debacle is to insist that a 2.4.X-preY should not be released as final 2.4.X until the pre's been out for a week, and there should never be any changes introduced into a final that didn't cook for a week as a pre.
I don't see the difference between a -rc that has cooked for a week, and a -pre that has cooked for a week, except that -rc sounds more like "this is *maybe* the next stable kernel", whereas -pre still sounds "beta".
That said, I think the week long delay is a *good* idea.
François
Quoted 11 lines · François Cami
Quoted 7 lines · Dan Kegel
2.4.x should continue to use -preY.
There's no need for a -rcY as some have suggested. All we need to do to avoid messes like the 2.4.15 debacle is to insist that a 2.4.X-preY should not be released as final 2.4.X until the pre's been out for a week, and there should never be any changes introduced into a final that didn't cook for a week as a pre.
Quoted 4 lines
I don't see the difference between a -rc that has cooked for a week, and a -pre that has cooked for a week, except that -rc sounds more like "this is *maybe* the next stable kernel", whereas -pre still sounds "beta".
The difference between "this is *maybe* the next stable kernel" and "just another beta" is very slippery. I don't object to the -rc idea, but I don't think it's as valuable as all that.
Quoted 1 line
That said, I think the week long delay is a *good* idea.
It's the key to avoiding bad releases.
- Dan
Quoted 1 line · Dan Kegel
Fran�ois Cami wrote:
[...]
Quoted 3 lines
Quoted 1 line
That said, I think the week long delay is a *good* idea.
It's the key to avoiding bad releases.
Yep. Specially when new 2.5.X-preY or 2.5.X are generated at a rate of 2 or 3 a week. Look at the history of the kernel. This would only create even _more_ pressure to get new patches in, and that is bad.
When a freeze (or slush) is decreed at the very end, it makes sense. Remember that a large part of the success of Linux is due to "Release early, release often".
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513
Quoted 5 lines · Horst von Brand
Quoted 1 line · Dan Kegel
Fran?ois Cami wrote:
[...]
Quoted 7 lines
Quoted 3 lines
Quoted 1 line
That said, I think the week long delay is a *good* idea.
It's the key to avoiding bad releases.
Yep. Specially when new 2.5.X-preY or 2.5.X are generated at a rate of 2 or 3 a week. Look at the history of the kernel. This would only create even _more_ pressure to get new patches in, and that is bad.
2.5 doesn't have releases, just snapshots of the development.
Quoted 4 lines
When a freeze (or slush) is decreed at the very end, it makes sense. Remember that a large part of the success of Linux is due to "Release early, release often".
Remember we are talking about 2.4, not 2.5. Having more time between releases gives more time to test the pre releases. The point it to have good point (not like 2.4.11, 12, 14, or 15) releases for what is supposed to be *stable*.
Release 50 -pre kernels for 2.4, but make sure that the next release has had a chance to stabalize with the new changes.
MF
Quoted 12 lines · Dan Kegel
Quoted 11 lines · François Cami
Quoted 7 lines · Dan Kegel
2.4.x should continue to use -preY.
There's no need for a -rcY as some have suggested. All we need to do to avoid messes like the 2.4.15 debacle is to insist that a 2.4.X-preY should not be released as final 2.4.X until the pre's been out for a week, and there should never be any changes introduced into a final that didn't cook for a week as a pre.
Quoted 9 lines
Quoted 4 lines
I don't see the difference between a -rc that has cooked for a week, and a -pre that has cooked for a week, except that -rc sounds more like "this is *maybe* the next stable kernel", whereas -pre still sounds "beta".
The difference between "this is *maybe* the next stable kernel" and "just another beta" is very slippery. I don't object to the -rc idea, but I don't think it's as valuable as all that.
IMHO, -rc is just one extra unnecessary entity and may bring only some confusion to newbies & extra work for maintaner.
Cheers,
Vitaly.