[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bits from the Release Team: Let's Fork(y)!



Hi,

On 9th August 2025 we released Debian 13 "trixie".

There are too many people who should be thanked for their work on getting
us to this point to list them all individually, and we would be sure to
miss some. Nevertheless, we would like to particularly thank the installer
team, the buildd and ftp teams, the images team, the publicity team, the
webmasters, the Release Notes editors, porters and all the bug squashers,
NMUers, package maintainers and translators who have contributed to making
trixie a great release of which we should all be proud.

Development of Debian 14 "forky"
================================

You will soon be able to upload to unstable once again for migrations to
forky, the new testing suite. FTP masters will re-enable the archive
maintenance scripts shortly for upload processing, and the britney
migration scripts will follow in the next couple of days.

loong64
=======

We expect to be in a position to start accepting packages built for loong64
into forky very soon (subject to architecture qualification later in the
cycle).

First point release for trixie
==============================

13.1 is scheduled for 6th September 2025. The stable release managers will
provide further details about this and future point releases very soon.

Please follow the guidance issued by them for fixes you wish to include in
the first point release, and remember to use reportbug for accurate
metadata in your requests.

For now, the release team is taking a break after a busy release day and
will be back to work on forky soon.

For the Release Team:
-- 
Jonathan Wiltshire                                      jmw@debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Attachment: signature.asc
Description: PGP signature


Reply to: