2.6.18-stable release plans?
Is there going to be another 2.6.18-stable release?
Quoted 8 lines · Chuck Ebbert
Is there going to be another 2.6.18-stable release?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Now that 2.6.19 is out, most likely not. -stable releases are made for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one -stable patches are made for (2.6.16 is an exception)..
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 4 lines · Jesper Juhl
Now that 2.6.19 is out, most likely not. -stable releases are made for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one -stable patches are made for (2.6.16 is an exception)..
Earlier I was going through the stable paches which apply for these kernel version:
http://kernelnewbies.org/Linux_2_6_19
http://kernelnewbies.org/Linux_2_6_18
http://kernelnewbies.org/Linux_2_6_16
I have to dig deep into the patch & kernel version to understand what are the features/implementations or fixes (patch). Problem here is 2 ways:-
1) Identifying which is a better kernel (features) for Desktop/Embedded/Server (I know, info mentioned in Changelog. But still...)
2) Easily knowing which stable patch applies for which arch or sub system (better way)
Proposal: Can maintainers implement this for better understanding of the Linux community (picking the best kernel or patch for the requirement) by adding a column on www.kernel.org home page?
Examples:
The latest stable version of the Linux kernel is: 2.6.19.2
*networking subsystem* 2007-01-10 19:11 UTC F V VI C Changelog
The latest prepatch for the stable Linux kernel tree is: 2.6.20-rc5
*x86 32/64* 2007-01-12 19:29 UTC B V VI C Changelog
Quoted 2 lines
--
Jesper Juhl <[email protected]>
Thanks,
Akula2
Quoted 8 lines · Sunil Naidu
I have to dig deep into the patch & kernel version to understand what are the features/implementations or fixes (patch). Problem here is 2 ways:-
1) Identifying which is a better kernel (features) for Desktop/Embedded/Server (I know, info mentioned in Changelog. But still...)
Quoted 6 lines
2) Easily knowing which stable patch applies for which arch or sub system (better way)
Proposal: Can maintainers implement this for better understanding of the Linux community (picking the best kernel or patch for the requirement) by adding a column on www.kernel.org home page?
...
This would be hard to organize and support. There are news sites like LWN which give outlines of important kernel changes, and there are mailinglists or community sites for architectures or driver subsystems if you are interested in special platforms or drivers, and there is the git repository metadata (via gitweb or directly from a locally cloned git repo).
I for one am actually posting release notes to a users' mailinglist of the drivers I'm interested in. But I can do this only because these are drivers with very low rate of fixes or feature additions.
It's also not only a question of who writes such release notes, but also of who the intended audience is. How fine-grained should the release notes be?
Anyway --- if in doubt, your distributor's current kernel is the best one.
Signature · 3 lines
Stefan Richter -=====-=-=== ---= =-=== http://arcgraph.de/sr/
Quoted 7 lines · Stefan Richter
This would be hard to organize and support. There are news sites like LWN which give outlines of important kernel changes, and there are mailinglists or community sites for architectures or driver subsystems if you are interested in special platforms or drivers, and there is the git repository metadata (via gitweb or directly from a locally cloned git repo).
That's the problem all about. I don't have problems finding info about a kernel feature or about a driver patch. But even for me it takes some time to figure it out. (I don't work only with Linux......do work with Mac OS, and Solaris too. But less of Windows!)
Am talking from the Linux users point of view (who need to know deep about the Kernel development, etc. Imagine, a student or a professional who wants to build a kernel with a patch for a i686 machine? Can't we simplify this at www.kernel.org home page instead of user being lost in searching on Google or wherever?
Quoted 3 lines
It's also not only a question of who writes such release notes, but also of who the intended audience is. How fine-grained should the release notes be?
I would like to contribute here, in any way. Fine graining might be a problem. But we can give info in general? Example, if patch-2.6.19.3 comes out - simply we can say as *x86 32/64* based on the weightage of fixes in that patch. What do you say?
Quoted 1 line
Anyway --- if in doubt, your distributor's current kernel is the best one.
I never depend on a distributor's kernel, especially Fedora has a Generic one with many things enabled into the kernel. The moment I install a distro....my hands would be itchy to build my own kernel which is very specific to my H/W. No less or more. In this way I can live with my best made kernel ;-)
[OT] Some posts I send does not appear on LKML. Even this one, I couldn't find on list :( What might be the problem?
Quoted 1 line
Stefan Richter
Thanks,
~Akula2
Sunil Naidu wrote:
...
Quoted 4 lines
Am talking from the Linux users point of view (who need to know deep about the Kernel development, etc. Imagine, a student or a professional who wants to build a kernel with a patch for a i686 machine?
You speak of advanced users with very special requirements. They can watch respective mailinglists, git trees, bugzillas, ... The file MAINTAINERS contains some pointers for them.
...
Quoted 3 lines
But we can give info in general? Example, if patch-2.6.19.3 comes out - simply we can say as *x86 32/64* based on the weightage of fixes in that patch. What do you say?
This cannot be measured objectively.
Signature · 3 lines
Stefan Richter -=====-=-=== ---= =-=== http://arcgraph.de/sr/
Quoted 8 lines · Jesper Juhl
Quoted 2 lines · Chuck Ebbert
Is there going to be another 2.6.18-stable release?
Now that 2.6.19 is out, most likely not. -stable releases are made for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one -stable patches are made for (2.6.16 is an exception)..
Great... just as 2.6.18 approaches actual stability.
Adrian, how much longer are you going to support 2.6.16? Would you consider moving to 2.6.18 any time soon?
Quoted 5 lines · Chuck Ebbert
Quoted 4 lines · Jesper Juhl
Quoted 2 lines · Chuck Ebbert
Is there going to be another 2.6.18-stable release?
Quoted 8 lines
Quoted 4 lines
Now that 2.6.19 is out, most likely not. -stable releases are made for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one -stable patches are made for (2.6.16 is an exception)..
Great... just as 2.6.18 approaches actual stability.
Adrian, how much longer are you going to support 2.6.16? Would you consider moving to 2.6.18 any time soon?
I'll continue to maintain 2.6.16 - moving to 2.6.18 or any other kernel would defeat the purpose of what I am doing.
I'm not yet decided whether I'll create other stable kernel branches, but it this will happen it won't be 2.6.18, more like 2.6.25 or 2.6.30.
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 3 lines · Jesper Juhl
Now that 2.6.19 is out, most likely not. -stable releases are made for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one -stable patches are made for (2.6.16 is an exception)..
There's generally a bit of overlap. 2.6.17.14 was about the same time as 2.6.18.1, and 2.6.18.6 was after 2.6.19.1. But 2.6.18.x must be over now, because the -stable team didn't release a 2.6.18.7 to match 2.6.19.2, and all of 2.6.x except for 2.6.19.2 has that weird file corruption bug (although rarely triggered).
-Daniel
*This .sig left intentionally blank*