Ever get miffed reading about a major new Ubuntu release only to learn it doesn't come with the newest Linux kernel? Well, that'll soon be a thing of the

Canonical’s announced a major shift in its kernel selection process for future Ubuntu releases. An “aggressive kernel version commitment policy” pivot will see it ship the latest upstream kernel code in development at the time of a new Ubuntu release.

Original announcement: Kernel Version Selection for Ubuntu Releases

  • Cows Look Like Maps@sh.itjust.works
    521·
    3 months ago

    I’m surprised by this decision, since Ubuntu’s strength is stability and by extension, friendliness to new users. Imo, a better move would be to ship a separate “unstable” release with non-LTS kernels.

    • infeeeee@lemm.ee
      31·
      3 months ago

      Maybe stability is not a frequent issue nowadays, and they need the new kernel to support new hardware more quickly?

      E.g. I can imagine a new linux friendly laptop can’t be sold with ubuntu preinstalled because the old kernel is not supporting some parts yet, but it’s already merged upstream. Or something like that.

        • infeeeee@lemm.ee
          10·
          3 months ago

          I just read the article and they say exactly what I guessed:

          “This approach would guarantee stability on the appointed release day, but was proving unpopular with consumers looking to adopt the latest features and hardware support as well as silicon vendors looking […] to align their Ubuntu support,” Canonical’s Brett Grandbois explains.

          But to “provide users with the absolute latest in features and hardware support, Ubuntu will now ship the absolute latest available version of the upstream Linux kernel at the specified Ubuntu release freeze date, even if upstream is still in Release Candidate (RC) status.”

    • Avid Amoeba@lemmy.ca
      6·
      3 months ago

      The announcement has some wording on treating LTS releases differently. My guess is they’ll be more aggressive on non-LTS releases and less aggressive in LTS, in order to preserve stability for LTS. Besides, non-LTS releases have been decidedly unstable for a while now, especially after the move to shorten their support lifespan. And it makes sense. They more or less serve as testing releases for the next LTS. Point being that whoever wants stability uses LTS anyway and they’re likely to adjust the new kernel selection process to keep that stability.