6 ms·

The timing is a little unfortunate. 5.6 will be too late to make it in for 20.04, but 5.5 isn't an LTS kernel and 20.04 is an LTS distribution, so I understand

by thayne 7y ago

The timing is a little unfortunate. 5.6 will be too late to make it in for 20.04, but 5.5 isn't an LTS kernel and 20.04 is an LTS distribution, so I understand not wanting to use 5.5.

SlowRobotAhead 7y ago
The issue of a rigid release schedule! April means April whether you miss out on something or not.
- m-p-3 7y ago
  You still end up having to make compromises no matter what.
  - thegeekpirate 7y ago
    One method allows for you to determine which compromises are acceptable, while the other does not.
    - Dylan16807 7y ago
      Not really. Let's consider an alternate flexible version that stretches up to 2-3 months outside of emergencies. Versus a non-flexible version that stretches 0 months outside of emergencies. If you compare the flexible version targeted at June, and the non-flexible version targeted at August, you'll find that they're making almost the exact same compromises. Nothing ever stops you from using an earlier version if it's more stable. So both schedules get to chose from multiple versions. Maybe flexible chooses from 6 month old to 3 months in the future code, via delaying. But non-flexible can choose from 9 month old to 0 month old code. It works out the same, and the only difference is how you label it.
derefr 7y ago
I'm kind of curious why Canonical don't simultaneously release a non-LTS release at the same time as the LTS release, to continue the flow of non-LTS releases. It seems like it'd make gearing up for the "LTS + 6mo" non-LTS release easier. Plus, then there'd be a clear non-LTS release to attribute any backported update packages to (that show up before they cut the "LTS + 6mo" non-LTS release.)
- pkaye 7y ago
  They do keep latest kernel PPAs for those who want to experiment. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/
- slgeorge 7y ago
  When I was involved we did LTS, and then half the distro team was focused on the LTS .1 release which happens 3 months later. The reality of software is that no amount of internal testing is the same as the amount of bug reports you get after the release. And, for an LTS as it's going to be around for a long time getting fixes in is more important - with a standard release you can choose to leave some that you'll resolve in the next six month release. The reality of doing LTS, plus LTS .1 mean that the next standard release didn't get as much attention. So in reality the first six month release was often very rough, with a lot of new things in it that would be straightened out over the course of the entire cycle. As someone mentions later in the thread Canonical started doing HWE releases, which means you can run a later kernel on the LTS. So I'm running 18.04.4 (I think) which has a HWE kernel that is newer than the one that originally shipped - not just security fixes but newer hardware compatibility.
- shrimp_emoji 7y ago
  ITT: why Manjaro's nerfed rolling is best model while point releases are a server meme.

by thayne 7y ago

The timing is a little unfortunate. 5.6 will be too late to make it in for 20.04, but 5.5 isn't an LTS kernel and 20.04 is an LTS distribution, so I understand not wanting to use 5.5.

SlowRobotAhead 7y ago

The issue of a rigid release schedule! April means April whether you miss out on something or not.

m-p-3 7y ago
You still end up having to make compromises no matter what.
- thegeekpirate 7y ago
  One method allows for you to determine which compromises are acceptable, while the other does not.
  - Dylan16807 7y ago
    Not really. Let's consider an alternate flexible version that stretches up to 2-3 months outside of emergencies. Versus a non-flexible version that stretches 0 months outside of emergencies. If you compare the flexible version targeted at June, and the non-flexible version targeted at August, you'll find that they're making almost the exact same compromises. Nothing ever stops you from using an earlier version if it's more stable. So both schedules get to chose from multiple versions. Maybe flexible chooses from 6 month old to 3 months in the future code, via delaying. But non-flexible can choose from 9 month old to 0 month old code. It works out the same, and the only difference is how you label it.

derefr 7y ago

I'm kind of curious why Canonical don't simultaneously release a non-LTS release at the same time as the LTS release, to continue the flow of non-LTS releases. It seems like it'd make gearing up for the "LTS + 6mo" non-LTS release easier. Plus, then there'd be a clear non-LTS release to attribute any backported update packages to (that show up before they cut the "LTS + 6mo" non-LTS release.)

pkaye 7y ago
They do keep latest kernel PPAs for those who want to experiment. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/
slgeorge 7y ago
When I was involved we did LTS, and then half the distro team was focused on the LTS .1 release which happens 3 months later. The reality of software is that no amount of internal testing is the same as the amount of bug reports you get after the release. And, for an LTS as it's going to be around for a long time getting fixes in is more important - with a standard release you can choose to leave some that you'll resolve in the next six month release. The reality of doing LTS, plus LTS .1 mean that the next standard release didn't get as much attention. So in reality the first six month release was often very rough, with a lot of new things in it that would be straightened out over the course of the entire cycle. As someone mentions later in the thread Canonical started doing HWE releases, which means you can run a later kernel on the LTS. So I'm running 18.04.4 (I think) which has a HWE kernel that is newer than the one that originally shipped - not just security fixes but newer hardware compatibility.
shrimp_emoji 7y ago
ITT: why Manjaro's nerfed rolling is best model while point releases are a server meme.