Canonical Takes Over Maintenance Of The Linux 4.2 Kernel

[phoronix]

Phoronix: Canonical Takes Over Maintenance Of The Linux 4.2 Kernel

With Greg Kroah-Hartman being done with maintaining the Linux 4.2 kernel, Canonical's Kernel Team has stepped up to provide maintenance...

http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.2-Canonical-Team

[GreatEmerald]

Hm, interesting, they are also doing that with 3.19. Yet that's not reflected on kernel.org. Hmm...

[bregma]

But... but everyone knows that Canonical don't ever contribute back upstream.

[ColinIanKing]

But... but everyone knows that Canonical don't ever contribute back upstream.

I do hope that is sarcasm.

git log --author=canonical --oneline | wc -l
1651

It's not much, but it's not nothing either.

[hoohoo]

Soon 4.2 kernel will send all your command lines to Amazon for marketing!!!!!

[hiddenmaverick]

Hm, interesting, they are also doing that with 3.19. Yet that's not reflected on kernel.org. Hmm...

Yeah, it would be nice for kernel.org to include some information about third-party LTS efforts, even if they currently don't do so.

However, Canonical maintains their list of maintained LTS kernels here: https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable

[Slaeppa]

That is typical waste of resources in the linux world. Kernel 4.3 is current stable in kernel.org and that works fine in ubuntu machines. What they could do is to package arch linux patches for amd crimson driver. Now big linux organization stops clients using lates techonlogy.

Ever heard of server environments? LTS-kernels are more than welcome, even Debian started to do LTS distro releases after squeeze. In smaller farms it might take months to upgrade distro, larger farms may take up to a year. Then comes kernel updates with release cycle of about 2-4 months, i wouldn't wan't to risk booting everything in ~3-month cycle.

For desktop or gaming use it of course won't matter.

[SystemCrasher]

There is more fancy release: kernel 4.1.15 has finally arrived and K-H even changed code name to hail T-800 https://lkml.org/lkml/2015/6/29/492

[SystemCrasher]

i wouldn't wan't to risk booting everything in ~3-month cycle.

This means that either you're cool enough to use stuff like live kernel patching, fixing most pressing issues on the fly, or you're just dumbass enough to run with unpatched kernel for a while. I wonder which is a case. And real productions these days can also use cool stuff like live migration, or just proper distributed system architecture, to be able to shut down particular piece of hardware for maintenance/repair/update wherever they need without any service interuption.