Ubuntu has announced an ‘important policy update’, making beta releases mandatory for all Ubuntu flavours, no exceptions.
Most flavours already hit the beta milestone every six months without issue. But until now a flavour that missed the deadline could still be granted a one-off exception.
During the Ubuntu 26.04 LTS cycle, that’s what happened with Ubuntu Kylin, the Chinese-orientated spin that uses the UKUI desktop. It missed the Beta window but still made the final release.
That won’t happen again. To get an official stable release, a flavour now must have a beta release out the same time as every other flavour, as Canonical’s Oliver Reiche says in a mailing list announcement:
“To ensure that every flavor is fully prepared for the final release, please be advised that no flavor will be considered for an official release unless it has successfully submitted a Beta release according to the scheduled timeline”.
For users of flavours, this has an obvious upside: a more stable stable release come April or October.
Daily builds allow for testing too, but tend to shift day-to-day (and mostly reach the same narrow set of ardent users). A beta freezes one snapshot and names it, so a wider pool are testing the same build, components and package set.
Per the announcement, package diffs between beta and final releases should be minimal and limited to bug fixes (though there is an official mechanisms to land features late too, namely Feature Freeze Exceptions).
But by making beta a hard requirement it will mean flavour developers know exactly which bugs they need to fix, and by when. Ostensibly, this news is more of a clarification than a major change. Most flavours that release, do take part in betas.
Do you think this clarification will improve stability, or is too strict on smaller flavour teams, some of whom are struggling to attract and retain contributors? Let me know in the comments.
Instagram Engineering
Shopify Engineering