Which indeed makes it a quite rushed release.
So i've been using ubuntu for many years (my first release was 6.06). Updating to a new release never worked. Around 12.04 times (when I started to seriously feel the need for stability) i started to only to LTS-to-LTS update, which basically meant a full reinstall, but once every two years was a more manageable.
Nowadays I run fedora, so far the upgrade experience has been incredibly great. I already did three versions jumps (36 to 37, 37 to 38, 38 to 39) and it didn't break.
That was a lot rougher than my experience upgrading from 20.04 -> 22.04, which went off without a hitch.
I'm sure they have added a few patches, but seems like they could have shipped fewer basing off .5+ ?
For the entire lifecycle (bar HWE kernel), it will remain at 6.8.0 and the number after - will be incremented with upstream and their own patches.
Existing binary code should work (unless it interfaces with 32-bit code in some affected way), but external packages need to include new dependencies.
If you set up ozone platform using chrome://flags, it will affect you. You can start with manually specifying --ozone-platform and then in chrome://flags, set ozone platform back to default.
After that a clean install of Ubuntu 24.04 LTS on the same machine worked, but after installing the latest Chrome on top of this, it won't start. After installing the latest Slack, that won't start either. BitWarden from the snap store will start, but after logging in, I get a endless spinner instead my vault contents. It is hard to believe that the Chrome/Slack/BitWarden issues are user error.
I'm not sure I've ever seen such a rough LTS release. I still wonder if this is just somehow me since surely they wouldn't release it without Chrome and Slack working, but I can't see what I could have done wrong just following the directions here.