Kernel Releases
Quoted 11 lines
Re: Kernel Releases
Quoted 4 lines
Development kernels are development kernels... nothing else. Look to distributors for high degrees of quality assurance testing. When you run a development kernel you have joined the development team, even if you don't know it. Finding and reporting bugs is your job...
That's why you stay away from 2.5.x, or 2.4.x-pre, or 2.4.x-ac -- which are development kernels. 2.4.x kernels are released kernels.
The point being made (I believe) is that recently the "released"
kernels have had a low quality with showstopper-quality bugs being introduced, but not detected, very late in the -preX cycle. What the initiator of this thread wants is a longer testing of the last -preX version. And changes between that an the "release" confined to bug/doc fixing *only*. Whether this has to be under the "-rcX" label, or not - the idea behind it is sound.
Martin
Signature · 5 lines
------------------------------------------------------------------ Martin Knoblauch | email: [email protected] TeraPort GmbH | Phone: +49-89-510857-309 C+ITS | Fax: +49-89-510857-111 http://www.teraport.de | Mobile: +49-170-4904759
Quoted 7 lines · Martin Knoblauch
The point being made (I believe) is that recently the "released"
kernels have had a low quality with showstopper-quality bugs being introduced, but not detected, very late in the -preX cycle. What the initiator of this thread wants is a longer testing of the last -preX version. And changes between that an the "release" confined to bug/doc fixing *only*. Whether this has to be under the "-rcX" label, or not - the idea behind it is sound.
I tend to agree with the idea of a -rcX labeling for -pre trees that the maintainer thinks are 'pretty much ready'. But, it is up to the maintainers of the relevant trees to accept such an idea, and be willing to hold off on new and exciting patches while testing and bugstomping is going on.
--
-- John E. Jasen ([email protected])
-- In theory, theory and practise are the same. In practise, they aren't.
John Jasen <[email protected]> said:
[...]
Quoted 5 lines
I tend to agree with the idea of a -rcX labeling for -pre trees that the maintainer thinks are 'pretty much ready'. But, it is up to the maintainers of the relevant trees to accept such an idea, and be willing to hold off on new and exciting patches while testing and bugstomping is going on.
AFAIU, if Linus (or whoever) puts out a -preX, it is because according to _their_ testing (limited, whatever) it is "almost done, please check". If they put out a non-pre, it is because they don't see any more issues with it. The _only_ way they can ever know something breaks is that _somebody_ (yes, I _do_ mean you) checks it out and complains beforehand.
Want to have Linux for a free ride? Sorry, pal, no deal. You can use it in exchange for testing and bug reports. Better yet, patches.
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
AFAIU, if Linus (or whoever) puts out a -preX, it is because according to _their_ testing (limited, whatever) it is "almost done, please check". If they put out a non-pre, it is because they don't see any more issues with it. The _only_ way they can ever know something breaks is that _somebody_ (yes, I _do_ mean you) checks it out and complains beforehand.
This is not always correct.. I've seen countless -pre kernels released as synch points with a warning in the changelog.
It is a matter of not messing with pre series kernels unless you are willing to read the changelogs.
Gerhard
--
Gerhard Mack
<>< As a computer I find your faith in technology amusing.