Skip to content

Ubuntu 12.04 LTS expires next month, but there’s the Dodo club

So Precise Pangolin was published as Ubuntu 12.04 LTS on April 26, 2012.

That’s a long time ago. Back then, Battleship, The Avengers (3D) and Cabin In The Woods (3D) were released. Intel released the Ivy Bridge Microarchitecture. The last proper US president campaigned for his second term and the US weren’t a failed state back then. It was a different world.

Since then, Ubuntu has seen the 12.10, 13.04, 13.10, 14.04 LTS, 14.10, 15.04, 15.10, 16.04 LTS and 16.04 releases, and the 17.04 release is due RSN. That’s 10 Ubuntu releases and two of them are LTS.

You should have upgraded since then. Twice. At least. If you haven’t:

You suck.
Your Devops is weak.
And you should feel bad.

Anyway: Support for 12.04 ends in a month.

If you want to join the Dodo club, though, together with the worlds remaining XP users, you can pay. Because there is the Ubuntu 12.04 Extended Security Maintenance subscription. It’s Ubuntu 12.04, and it’s extended and it’s probably maintenance, but it certainly has nothing to do with “security”. That would mean upgrading.

Published inComputer ScienceHackerterrorcybercyber

4 Comments

  1. Woo

    Security fixes in 5+ Jahre alte Sourcen zurueckporten stelle ich mir auch als einen ganz eigenen Kreis der Hoelle vor…

  2. Daniël van Eeden

    Reminds me of Solaris Vintage support where you had a subscription to be allowed to pay Sun to backport security patches..

  3. Woo

    … wobei ich sagen muss, dass so ziemlich alle groesseren Distros dringend an ihren Upgrade-Mechanismen arbeiten muessen. Fuer Redhat/Centos gibts seit Jahren keine offiziell supportete Upgrade-Mechanik, und die inoffizielle richtet teilweise massiven Flurschaden an. Bei Debian gehts “einigermassen” bzw mit geringen Nacharbeiten. SuSE ist auch weit im Voodoo-Bereich was die Erfolgsquoten angeht. Sowas ist fuer Server-OSes einfach unzulaenglich.

    • kris kris

      I believe your approach is broken.

      You don’t upgrade, you redeploy a new build (which has been tested before in a blue/green deployment of the cluster).

      Do not layer state changes on top of state changes, that does not work. Create an immutable image from the new distro and whatever application is running in it, run that in a small test deployment, check that it works, then raise it to 100% deployed and undeploy the old image.

Leave a Reply

Your email address will not be published. Required fields are marked *