Skip to contentSkip to conversation

Latest kernel stable/longterm status

DISCUSSION Greg KH 6 participants 15 messages Jan 10, 2012 – Jan 21, 2012 Stable branch

lore
Share & tools
lore

Greg KH

author
#0 lore raw

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

First off, please everyone remember to mark any patch that you want to have applied to the stable kernel trees with a simple:
Cc: stable <[email protected]>
marking in the Signed-off-by: area. Once the patch hits Linus's tree, I will automatically be notified of it and it will be applied if possible. If it does not applied, you will be notified of that.

Note that the address is [email protected], not the older address that used to be used before October of 2011.

At this time, all stable and longterm kernel trees are being maintained in one big git tree, located at:
git.kernel.org:/pub/scm/linux/kernel/git/stable/linux-stable.git
There are different branches for every different major kernel version.

Here's the different active kernel versions that I am maintaining at the moment:

3.2.y - this will be maintained until 3.3 comes out
3.1.y - there will be only one, maybe two, more releases of this tree 3.0.y - this is the new "longterm" kernel release, it will be
maintained for 2 years at the minimum by me.
2.6.32.y - this is the previous "longterm" kernel release. It is
approaching it's end-of-life, and I think I only have another month or so doing releases of this. After I am finished with it, it might be picked up by someone else, but I'm not going to promise anything.

All other longterm kernels are being maintained in various forms (usually quite sporadically, if at all), by other people, and I can not speak for their lifetime at all, that is up to those individuals.

If anyone has any questions about any of this, please let me know.

thanks,

greg k-h

#1 lore raw
Quoted 2 lines · Greg KH

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

Thanks for all your hard work Greg!

Quoted 6 lines

Here's the different active kernel versions that I am maintaining at the moment:

3.2.y - this will be maintained until 3.3 comes out
3.1.y - there will be only one, maybe two, more releases of this tree 3.0.y - this is the new "longterm" kernel release, it will be
maintained for 2 years at the minimum by me.

I will also point out, that I plan on maintaining the 3.0.y-rtx release for just as long.

-- Steve

#2 lore raw
Quoted 6 lines · Steven Rostedt
Quoted 2 lines · Greg KH

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

Thanks for all your hard work Greg!

I'd also like to thank Greg.

Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu has also chosen 3.2 as a long term supported kernel for the 12.04 release and will pick up support for it when 3.3 is released.

Debian is still discussing which kernel to use for Wheezy, but Ben Hutchings has expressed strong interest in 3.2 on [email protected].

rtg

Signature · 1 line
Tim Gardner [email protected]
author
#3 lore raw
Quoted 5 lines · Tim Gardner
Quoted 4 lines · Steven Rostedt
Quoted 2 lines · Greg KH

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

Quoted 8 lines
Quoted 2 lines

Thanks for all your hard work Greg!

I'd also like to thank Greg.

Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu has also chosen 3.2 as a long term supported kernel for the 12.04 release and will pick up support for it when 3.3 is released.

What exactly do you mean by this?

greg k-h

#4 lore raw
Quoted 3 lines
Quoted 3 lines

Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu has also chosen 3.2 as a long term supported kernel for the 12.04 release and will pick up support for it when 3.3 is released.

Do you think you can do it for 5 years ? why not moving forward with 3.3 then 3.4 ?

#5 lore raw
In reply to Greg KH
Quoted 11 lines · Greg KH
Quoted 10 lines · Tim Gardner
Quoted 6 lines · Steven Rostedt
Quoted 2 lines · Greg KH

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

Thanks for all your hard work Greg!

I'd also like to thank Greg.

Quoted 7 lines
Quoted 3 lines

Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu has also chosen 3.2 as a long term supported kernel for the 12.04 release and will pick up support for it when 3.3 is released.

What exactly do you mean by this?

greg k-h

If you're agreeable, I would very much prefer to continue with the stable update model that you've developed by committing to the linux-2.6.32.y and linux-3.2.y branches in git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git. The mailing list review process as well as the policies regarding patch suitability are working well.

rtg

Signature · 1 line
Tim Gardner [email protected]
author
#6 lore raw
Quoted 18 lines · Tim Gardner
Quoted 17 lines · Greg KH
Quoted 5 lines · Tim Gardner
Quoted 4 lines · Steven Rostedt
Quoted 2 lines · Greg KH

As 3.2 is now out, here's a note as to the current status of the different stable/longterm kernel trees.

Quoted 8 lines
Quoted 2 lines

Thanks for all your hard work Greg!

I'd also like to thank Greg.

Ubuntu will continue to support 2.6.32.y until April 2015. Ubuntu has also chosen 3.2 as a long term supported kernel for the 12.04 release and will pick up support for it when 3.3 is released.

What exactly do you mean by this?

Quoted 7 lines
Quoted 1 line

greg k-h

If you're agreeable, I would very much prefer to continue with the
stable update model that you've developed by committing to the
linux-2.6.32.y and linux-3.2.y branches in git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git.
The mailing list review process as well as the policies regarding
patch suitability are working well.

As I previously stated, in this email, I already have someone lined up to maintain 2.6.32 after I am done with it, but I'm sure that person would love it if you would send any needed patches to [email protected] to help them out.

greg k-h

#7 lore raw
Quoted 7 lines · Greg KH

As I previously stated, in this email, I already have someone lined up to maintain 2.6.32 after I am done with it, but I'm sure that person would love it if you would send any needed patches to [email protected] to help them out.

greg k-h

I'm happy to work with whomever. Your original email with "it might be picked up by someone else, but I'm not going to promise anything" didn't seem that definite.

rtg

Signature · 1 line
Tim Gardner [email protected]
author
#8 lore raw
Quoted 7 lines · Tim Gardner
Quoted 6 lines · Greg KH

As I previously stated, in this email, I already have someone lined up to maintain 2.6.32 after I am done with it, but I'm sure that person would love it if you would send any needed patches to [email protected] to help them out.

Quoted 5 lines
Quoted 1 line

greg k-h

I'm happy to work with whomever. Your original email with "it might be picked up by someone else, but I'm not going to promise anything" didn't seem that definite.

Sorry, I didn't want to put words in the mouth of someone else, but given that Willy has done a great job with 2.4 and 2.6.16, I'm pretty sure he will continue to do well with 2.6.32.

thanks,

greg k-h

#9 lore raw

Hi Greg,

Quoted 10 lines · Greg KH
Quoted 9 lines · Tim Gardner
Quoted 7 lines · Greg KH

As I previously stated, in this email, I already have someone lined up to maintain 2.6.32 after I am done with it, but I'm sure that person would love it if you would send any needed patches to [email protected] to help them out.

greg k-h

Quoted 7 lines
Quoted 3 lines

I'm happy to work with whomever. Your original email with "it might be picked up by someone else, but I'm not going to promise anything" didn't seem that definite.

Sorry, I didn't want to put words in the mouth of someone else, but given that Willy has done a great job with 2.4 and 2.6.16, I'm pretty sure he will continue to do well with 2.6.32.

Thanks for the nice comment :-) Please note that I did not work on 2.6.16, Adrian did, I only worked on .20 and .27.

Yes I'm still interested in taking over 2.6.32 when you give it up. I must admit I've got quite silent last months, slowly trying to find time to backport 2.6.32 fixes into .27, and still a bit afraid by the added complexity of the new publication model. Time will tell. This weel-end I hope to be able to produce 2.6.27.60-rc1.

What is very important to me is that I want people to complain if they find that I'm too slow, as I don't want to degrade the quality of the stable series by taking a position someone would take better.

Thanks,
Willy

author
#10 lore raw
Quoted 17 lines · Willy Tarreau

Hi Greg,

Quoted 14 lines · Greg KH
Quoted 12 lines · Tim Gardner
Quoted 7 lines · Greg KH

As I previously stated, in this email, I already have someone lined up to maintain 2.6.32 after I am done with it, but I'm sure that person would love it if you would send any needed patches to [email protected] to help them out.

greg k-h

I'm happy to work with whomever. Your original email with "it might be picked up by someone else, but I'm not going to promise anything" didn't seem that definite.

Quoted 6 lines
Quoted 3 lines

Sorry, I didn't want to put words in the mouth of someone else, but given that Willy has done a great job with 2.4 and 2.6.16, I'm pretty sure he will continue to do well with 2.6.32.

Thanks for the nice comment :-) Please note that I did not work on 2.6.16, Adrian did, I only worked on .20 and .27.

Ah, you are right, sorry about that, too many different trees :)

But also note that Adrian didn't really follow the "stable rules", so I don't count that as proper maintaining of that tree.

Quoted 9 lines

Yes I'm still interested in taking over 2.6.32 when you give it up. I must admit I've got quite silent last months, slowly trying to find time to backport 2.6.32 fixes into .27, and still a bit afraid by the added complexity of the new publication model. Time will tell. This weel-end I hope to be able to produce 2.6.27.60-rc1.

What is very important to me is that I want people to complain if they find that I'm too slow, as I don't want to degrade the quality of the stable series by taking a position someone would take better.

I don't think you will do a bad job at all, You'll do fine, if you need any help, feel free to ask.

thanks,

greg k-h

#11 lore raw
Quoted 6 lines · Greg KH
Quoted 6 lines

Yes I'm still interested in taking over 2.6.32 when you give it up. I must admit I've got quite silent last months, slowly trying to find time to backport 2.6.32 fixes into .27, and still a bit afraid by the added complexity of the new publication model. Time will tell. This weel-end I hope to be able to produce 2.6.27.60-rc1.

Quoted 6 lines
Quoted 3 lines

What is very important to me is that I want people to complain if they find that I'm too slow, as I don't want to degrade the quality of the stable series by taking a position someone would take better.

I don't think you will do a bad job at all, You'll do fine, if you need any help, feel free to ask.

Yeah, I know you're always there to help me when I need, this is what keeps me going :-)

Cheers,
Willy

#12 lore raw
In reply to Greg KH
Quoted 6 lines · Greg KH

First off, please everyone remember to mark any patch that you want to have applied to the stable kernel trees with a simple:
       Cc: stable <[email protected]>
marking in the Signed-off-by: area.  Once the patch hits Linus's tree, I will automatically be notified of it and it will be applied if possible. If it does not applied, you will be notified of that.

How do you want us to specify to which versions it should be applied?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#13 lore raw
Quoted 9 lines · Geert Uytterhoeven
Quoted 6 lines · Greg KH

First off, please everyone remember to mark any patch that you want to have applied to the stable kernel trees with a simple:
       Cc: stable <[email protected]>
marking in the Signed-off-by: area.  Once the patch hits Linus's tree, I will automatically be notified of it and it will be applied if possible. If it does not applied, you will be notified of that.

How do you want us to specify to which versions it should be applied?

Cc v3.2, v3.1, ... <[email protected]>

?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

author
#14 lore raw
Quoted 9 lines · Geert Uytterhoeven
Quoted 8 lines · Geert Uytterhoeven
Quoted 6 lines · Greg KH

First off, please everyone remember to mark any patch that you want to have applied to the stable kernel trees with a simple:
� � � �Cc: stable <[email protected]>
marking in the Signed-off-by: area. �Once the patch hits Linus's tree, I will automatically be notified of it and it will be applied if possible. If it does not applied, you will be notified of that.

Quoted 3 lines
Quoted 1 line

How do you want us to specify to which versions it should be applied?

Cc v3.2, v3.1, ... <[email protected]>

That can work, or if you read Documenation/stable_kernel_rules.txt you can see some other ways to nicely do this :)

thanks,

greg k-h