Stonking Stingray is frozen and ships October 15 — here's how to test the release candidate, time your upgrade, and avoid the day-one traps.

Ubuntu 26.10 "Stonking Stingray" crossed into final freeze on Thursday, October 8. The release team announced that from here on, only release-critical fixes — bugs that break images or installers — and fixes fit for post-release stable updates will make it into the archive. Every remaining upload now has to reference a Launchpad bug report. Canonical is spinning final release-candidate images this week, and the target is still Thursday, October 15.

If you've watched Ubuntu cycles before, you know the script: the freeze is the quiet part, and release day is where the mistakes happen. Here's a five-day playbook for the gap in between.

Day 1–2: Grab the RC and test your actual hardware

Candidate images are being built for all the flavors right now. Download the release candidate for the flavor you actually run — not the one you wish you ran — and boot it on your real machine, ideally from a USB stick in "try" mode or on a spare partition.

What you're hunting for: Wi-Fi firmware that doesn't load, NVIDIA driver weirdness, Bluetooth pairing failures, and anything your laptop's fingerprint reader or webcam does (or doesn't do). Ubuntu 26.10 is shipping with a pre-release Linux 7.3 kernel — the kernel froze on October 1 while upstream 7.3 is still in release-candidate stage, with the stable 7.3 landing around October 18 (or October 25 if Linus needs an extra candidate). That means the RC you're testing boots a kernel the rest of the world hasn't finished yet. The finished 7.3 will arrive through normal updates shortly after release, so don't panic about the version string — but do report any driver regression you find now, while fixes can still be backported.

Also worth a look: this cycle completed the migration to Rust-based uutils coreutils, so cp, mv, and rm are no longer GNU code. Smoke-test your shell scripts and dotfiles against the RC if you live in the terminal.

Day 3: Pick your upgrade slot

Release day is not the only day you can upgrade. Three honest options:

  • Day one (Oct 15): for testers and people who enjoy reading changelogs. You get the newest bits and the first wave of forum threads.
  • Day seven: the sweet spot. The first point-fix updates and the finished 7.3 kernel will have landed, and the worst RC-era regressions will be documented.
  • Skip it: 26.10 is an interim release with nine months of support, ending around July 2027. If you run Ubuntu on anything that pays the bills, or your 26.04 LTS is behaving, staying put is a legitimate strategy. The new kernel capabilities will reach LTS users through hardware-enablement updates down the road.

Day 4: The pre-upgrade safety drill

However you time it, do the boring part first: take a full backup, and if you run Btrfs or LVM, snapshot the root filesystem before the upgrade starts. Write down your PPAs and third-party repositories — the upgrader disables them, and you'll need to re-enable them one by one afterward. Export your list of manually installed packages (apt-mark showmanual is your friend) so you can diff it if something goes missing.

Day 5: Upgrade, then verify like an operator

When you pull the trigger, watch the upgrade — don't kick it off and leave for lunch. After the reboot, verify the things that actually matter to your workflow: networking, graphics, audio, printing, and your VPN client. Check uname -r and note that you may be on a 7.3-rc kernel for a few days; run updates again the following week and confirm the finished 7.3 lands cleanly.

Final freeze weeks are the one time a distro is at its most honest — everything in the image is exactly what will ship, and every remaining bug is being triaged in the open. Five days of deliberate testing beats five hours of frantic troubleshooting on the 16th.

Sources