All people who might read this know that traditionally
stable releases are even numbered and development branches
are odd numbered. This changed during late develoment of
2.6, according to my analysis because of the "invention" of
GIT which was itself necessary because of BitKeeper (insert
ooooooooold flame-wars here) and which allowed very dynamic
develoment.
While this has been effective, alternative
voices (Mr Morton complaining that more bugs were added
than repaired, semi-stable semi-supported 2.6.x.y branches
where invented...) come more and more into the front.
The
upcoming GPL v3 versus v2 debate will make things worse,
and we all know this. The un-ending stable ABI argument
goes into this same direction.
You might think it's easy for me to simply "use" Linux and
complain while you're doing the hard stuff. As it happens,
the current development/stable model makes our life as
"users" more and more difficult.
I'm using Linux since 1997
on a Mac thanks to LinuxPPC-1997, and I'm a hard pusher of
Linux whenever possible, sometimes against the common
sense, for example when I favor using National Instrument
cards with Linux drivers and custom written TCP/IP server
against easy LabView on Windows. While some of you dislike
closed source drivers, the choices "we users" face are:
- closed source drivers with closed source OS
- closed source drivers with open source OS
Please consider that we are living in a REAL world, and not
Disney-Land.
So I've demonstrated that from a "users" perspective a newI don't think you have demonstrated that.
stable Linux would be of advantage. I'll now list what I
suggest for this new stable branch:
Why on earthIt sure is an object, it's even called object code. I think the name
call "kernel object" things that are "kernel modules" ? And
that every person calls "modules" and not "objects" ? I
know I know, in UNIX dynamic libraries are .so "shared
objects", so what ? A "module" is a "module" and NOT an
"object", call a cat a cat.
Third, while a stable ABI in a dynamically developed kernel
is a difficult/impossible/unwanted feature,
it should beIf they want to keep their drivers closed they get to do all the hard
possible to implement in a stable branch. This could even
be a distinction between "stable" and "development"
branches. And it would certainly help vendors of
closed-source drivers.