Ubuntu 26.10 final freeze is on the schedule for October 8, with final release-candidate builds also targeted to start today. The final release remains scheduled for October 15. The immediate deadline concerns maintainers: packages intended for the release images need to be uploaded before Thursday’s cutoff.
The build target changes; the release date stays put
Skia announced the Thursday target on October 5. Recent milestones began their first builds on the Monday of release week. For this release, that Monday would be October 12. The team is therefore targeting a start four calendar days earlier.
Those four days could help a tester report an installation failure and a developer investigate it. They are not four extra days after the final release. Nor does the notice establish that every flavor already has a candidate to download.
The dates to distinguish
- October 1: Ubuntu announced the 26.10 beta.
- October 8: scheduled final freeze and targeted start of final release-candidate builds.
- October 15: scheduled final release.
A tighter rule for image packages
Under Ubuntu 26.10 final freeze, release-critical, security-critical or exceptional fixes require confirmation from the Release Team and the team responsible for the package. Feature Freeze allowed ordinary bug-fix uploads to continue.
An unseeded universe package stays under Feature Freeze because it does not affect release images. A seed is the package selection for an image; the distinction concerns what the image includes, not how popular an application is.
Find the images containing a package
Ubuntu documents seeded-in-ubuntu, supplied by ubuntu-dev-tools, for this check. On a development system with those tools installed, run seeded-in-ubuntu followed by the package name. The output lists daily images containing it. Presence in an image cannot establish whether it works on your hardware.
Give a failure the right context
Ubuntu’s release-cycle documentation gives boot and installation faults particular attention during finalization. Other installed-system problems can receive Stable Release Updates. For a report to help that process, include the image date, hardware, installation path and steps that trigger the error.
Keep a clean-install result separate from an upgrade result. Likewise, a virtual machine tests virtual hardware, not a laptop’s physical wireless adapter. Our advice is to preserve a working installation and tested backup while assessing candidates on spare hardware or in a VM.
Our Ubuntu 26.10 beta report covered the October 1 milestone. Keep the image date beside those results. Success on a newer candidate can show a fix, rather than contradicting a beta failure. Watch for the Release Team’s call for testing to identify the intended candidates, and its final-release declaration to confirm the finished release.