RFD: Kernel release numbering
Quoted 20 lines · --- Jeff Garzik
Quoted 1 line · Greg KH
On Wed, Mar 02, 2005 at 05:15:36PM -0800, Linus Torvalds
Quoted 3 lines · wrote:
But when pressed about the issue of speed of development,
rate of
Quoted 1 line
change, feature increase, driver updates, and so on, no one
else has any
Quoted 1 line
clue of what to do. They respond with, "but only put
bugfixes into a
Quoted 1 line
stable release." My comeback is explaining how we handle
lots of
Quoted 1 line
different types of bugfixes, by api changes, real fixes, and
driver
Quoted 1 line
updates for new hardware. Sometimes these cause other bugs
to happen,
Quoted 1 line
or just get shaken out where they were previously hiding
(acpi is a
Quoted 1 line
great example of this issue.) In the end, they usually fall
Quoted 9 lines
back on
Quoted 1 line
muttering, "well, I'm just glad that I'm not a kernel
developer..." and
Quoted 1 line
back away.
The pertinent question for a point release (2.6.X.Y) would simply be
"does a 2.6.11 user really need this fix?"
no. If something is not working in 2.6.11 i will switch to 2.6.10 ;-) and _maybe_ report a bug
Quoted 8 lines
Quoted 2 lines
Like I previously said, I think we're doing a great job.
The current
Quoted 1 line
-mm staging area could use some more testers to help weed
out the real
Quoted 1 line
issues, and we could do "real" releases a bit faster than
every 2 months
Quoted 1 line
or so. But other than that, we have adapted over the years
Quoted 9 lines
to handle
Quoted 1 line
this extremely high rate of change in a pretty sane manner.
I think Linus's "even/odd" proposal is an admission that 2.6.X releases
need some important fixes after it hits kernel.org.Otherwise 2.6.X is simply a constantly indeterminent state.
Let me tell you what i understood from this thread:
2.6.12 "almost stable"
2.6.13 devel (new drivers,fixes and stuff -- may be broken) 2.6.14 (based on 2.6.13) tries to became stable again 2.6.15 also devel (see above)
2.6.16 (based on 2.6.15) also tries to became stable again
So we will _want_ to have a stable kernel (like 2.4 now) but this will never happen (see above)
Quoted 3 lines
We need to serve users, not just make life easier for kernel developers ;-)
You said it. Hopefully you will make our life easier and we (as testers) will make your's.
Quoted 2 lines
Jeff
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
Quoted 8 lines · szonyi calin
Let me tell you what i understood from this thread:
2.6.12 "almost stable"
2.6.13 devel (new drivers,fixes and stuff -- may be broken) 2.6.14 (based on 2.6.13) tries to became stable again 2.6.15 also devel (see above)
2.6.16 (based on 2.6.15) also tries to became stable againSo we will _want_ to have a stable kernel (like 2.4 now) but this will never happen (see above)
No. Linus' proposal was shouted down.
What is happening is that Linus will continue to release 2.6.x as usual, with no even/odd stuff.
Then a review committee will maintain 2.6.x.y (where y starts at 1 and increments). This will contain obvious fixes against 2.6.x. When Linus comes out with 2.6.x+1, then they will start a new stable tree 2.6.x+1.y.
Please see the thread entitled "[RFC] -stable, how it's going to work.", started by Greg KH for more information on the "stable" release process.
Chris