Debian 12 “Bookworm” Just Hit its First Freeze

Development on Debian 12 “Bookworm” just hit a major milestone.

Ahead of its expected release later this year, the popular Linux distro has officially entered a freeze period.

Paul Gevers, writing on behalf of the Debian release team, announced the first freeze on the Debian developer mailing list, writing:

“On January 12th we stopped accepting transition requests and we are working to complete the transitions in progress. We ask the maintainers of packages that are part of the toolchain to stop uploading those packages without prior approval from us.”

3 further freeze milestones are planned:

  • February 12 – Soft Freeze
  • March 12 – Hard Freeze
  • TBD – Full Freeze

The date for the final “Full Freeze” is yet to be determined but will occur shortly before the final stable release of Debian 12.

As per the Debian 12 Freeze policy:

“During the Full Freeze, all packages can only migrate to testing after manual review by the release team. For key packages and packages without autopkgtests, the rules stay the same. From the start of the full freeze, those rules will also apply to other packages.”

Amongst a significant set of package, toolchain, and kernel uplifts, Debian 12 will feature a new version of the Debian Installer, and a visual refresh with brand new artwork.

More details on Debian 12 can be found in the WIP release notes.

Print Friendly, PDF & Email

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Server Status

Aradippou Chat 1 Chat 2 Larnaca Limassol Nicosia

Chat Links

Official Links.

1. Chat 1.
2. Chat 2.

Alternative Mirror Links.

1. KiwiIRC 1.
2. KiwiIRC 2.

Other Web Clients.

1. IrcCloud.

Recent Posts

Related Posts:

Advertisement

Archives

Super Club Radio

Mighty Deals

CyIRC

CyIRC Tweets

Scroll Up
Fatal error: Uncaught WMAC\JSMin_UnterminatedStringException: WMAC\JSMin: Unterminated String at byte 1180: "+o.accessToken}}).then(e=>{if(!e.ok)throw e;return e});return a.catch(e=>{console.error(`Failed to logout chatrix session. deviceId: ${o.deviceId}`)}),a}})(); in /home/bszucbfe/public_html/wp-content/plugins/clearfy/components/minify-and-combine/includes/classes/ext/php/jsmin.php:215 Stack trace: #0 /home/bszucbfe/public_html/wp-content/plugins/clearfy/components/minify-and-combine/includes/classes/ext/php/jsmin.php(157): WMAC\JSMin->action(2) #1 /home/bszucbfe/public_html/wp-content/plugins/clearfy/components/minify-and-combine/includes/classes/ext/php/jsmin.php(96): WMAC\JSMin->min() #2 /home/bszucbfe/public_html/wp-content/plugins/clearfy/components/minify-and-combine/includes/classes/class-main.php(375): WMAC\JSMin::minify('(function(){"us...') #3 /home/bszucbfe/public_html/wp-includes/class-wp-hook.php(324): WMAC_PluginMain->jsSnippetcacher('(function(){"us...', '/home/bszucbfe/...') #4 /home/bszucbfe/public_h in /home/bszucbfe/public_html/wp-content/plugins/clearfy/components/minify-and-combine/includes/classes/ext/php/jsmin.php on line 215