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

Bits from the Release Team: checks, calendars, and cleanups



Hello,

Lintian data in britney
-----------------------

The software that manages package migrations from unstable to testing
(britney) can now consume lintian data directly. The results are supplied
through UDD and give britney a new way to apply quality checks when
deciding whether a package may migrate.

Lintian runs on the built binary packages, which means these checks can
only be performed after a successful build - not as part of a source-only
upload to unstable. By making the results available inside britney, we can
use them consistently as part of migration policy rather than leaving them
only to manual review.

First LintianPolicy check: /usr-merge
-------------------------------------

The first check enabled through this new framework focuses on
`/usr-merge`. Packages that still install files into aliased locations
are now prevented from migrating to testing.

This builds on the project-wide cleanup completed for trixie and helps
ensure the archive remains consistent. Further checks may be added where
they support the project's release quality objectives.

armel removal from forky
------------------------

The armel architecture has now been removed from the forky suite. This
port supported very old ARM systems without hardware floating-point,
such as early plug computers and NAS devices.

As development effort increasingly focuses on newer ARM hardware (armhf
and arm64), armel is no longer part of forky.

Point release timetable
-----------------------

Stable point releases for trixie, and the remaining point releases for
bookworm, now follow a published timetable rather than being announced
one by one. This gives maintainers, derivatives, and users clear dates
to plan around.

The change was announced in the most recent Bits from the Stable Release
Managers:
https://lists.debian.org/debian-devel-announce/2025/08/msg00003.html

The up-to-date timetable will be maintained on the Release Team pages:
https://release.debian.org/

The dates are provisional and may change if urgent issues arise, but the
aim is to provide a predictable schedule wherever possible.

Release Team iCal feed
----------------------

The Release Team maintains an iCalendar feed with key dates, including
point releases, freezes, and other milestones. It can be imported into
most calendar applications to make it easier to stay up to date:

https://release.debian.org/release-calendar.ics

The feed is kept current alongside announcements, so subscribing is a
straightforward way to track the release timetable.


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: