Debian Freeze for Squeeze Policy Reconsidered
The Debian release team decided on July 29 to adopt a two-year development freeze cycle for its 6.0 "Squeeze" release. A day's worth of discussion to follow led the team to revise its plans again.
According to Debian's decision, freezes are to happen in the December of odd-numbered years, with releases in the following even-numbered year. According to this plan the freeze for the next major version "Squeeze" should have been December 2009 with its release in the first half of 2010. Only a day later, things changed again along the lines of "that was then, this is now" with a follow-up announcement.
Considering the release goals and "in consideration of the Debian community's feedback to the release team's initial announcement," the team decided to "revisit its decision on December 2009 as the proposed freeze date" as part of its latest news releases. Early September would bring a new timeline announcement. "Debian community's feedback" could be a euphomism for some of the enraged responses from project circles who were gearing themselves for a definitive freeze timeline. Part of the confusion could have come from media misinterpretation that a freeze cycle meant a release cycle.
The distinction proves to be fairly minor, however, unless you consider that the notorious "Sarge" release lasted one whole year in freeze status. A Debian "freeze" actually means "feature freeze," where no new features are integrated, only bug fixes. The release will then not go out until all Release Critical (RC) bugs are removed, which typically (and by Debian quality standards workably) takes half a year. A freeze in December would then provide a release more or less midway into the following year.
That a Debian release could possibly be planned for a specific year seemed to be blasphemous enough for many project adherents to bring them to the baricades. The deeper reason for a set-in-stone freeze date might also be coordinating the Debian and Ubuntu release dates, as Mark Shuttleworth has continually recommended in his call for a release "pulse." Many Debian developers, however, worry about getting into a disadvantaged situation with Ubuntu, with its "one generation ahead" policy, and possibly losing customers to them. Debian's attitude has always rather been "It's ready when it's ready."
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Fedora Asahi 40 Remix Available for Macs with Apple Silicon
If you've been anticipating KDE's Plasma 6 for your Apple Silicon-powered Mac, then you're in luck.
-
Red Hat Adds New Deployment Option for Enterprise Linux Platforms
Red Hat has re-imagined enterprise Linux for an AI future with Image Mode.
-
OSJH and LPI Release 2024 Open Source Pros Job Survey Results
See what open source professionals look for in a new role.
-
Proton 9.0-1 Released to Improve Gaming with Steam
The latest release of Proton 9 adds several improvements and fixes an issue that has been problematic for Linux users.
-
So Long Neofetch and Thanks for the Info
Today is a day that every Linux user who enjoys bragging about their system(s) will mourn, as Neofetch has come to an end.
-
Ubuntu 24.04 Comes with a “Flaw"
If you're thinking you might want to upgrade from your current Ubuntu release to the latest, there's something you might want to consider before doing so.
-
Canonical Releases Ubuntu 24.04
After a brief pause because of the XZ vulnerability, Ubuntu 24.04 is now available for install.
-
Linux Servers Targeted by Akira Ransomware
A group of bad actors who have already extorted $42 million have their sights set on the Linux platform.
-
TUXEDO Computers Unveils Linux Laptop Featuring AMD Ryzen CPU
This latest release is the first laptop to include the new CPU from Ryzen and Linux preinstalled.
-
XZ Gets the All-Clear
The back door xz vulnerability has been officially reverted for Fedora 40 and versions 38 and 39 were never affected.