Hi,
The Stable Release Managers, with the support of the rest of the Release
Team, are responsible for updates to the new stable release 'trixie' (and
oldstable 'bookworm' while it is also being supported by the Security
Team), via point releases and the stable-updates mechanisms [SUA].
You can see the current status of proposed updates to stable via our
BTS pseudo-package [BTS] and our tracking website. [QV]
Point release schedule
======================
A provisional schedule for point releases through to September 2026, when
oldstable is expected to become LTS, can be found at
https://release.debian.org and in our calendar.
The stable release receives an update in approximately one month's time,
followed by every two months. Oldstable is updated at approximately
four-month intervals. The schedule is subject to changes, and each point
release will be confirmed with an announcement to
debian-stable-announce@lists.debian.org.
As always, the first update to a new release will be very busy, so we ask
for your patience if you are still awaiting a reply to an upload request.
It may be that an update to your package is deferred to a later point
release purely from a workload perspective; more serious or more urgent
fixes will be prioritised.
Workflow
========
Uploads to a supported stable release should target their suite name in the
changelog, i.e. 'trixie' or 'bookwork'. You should normally use reportbug
and the release.debian.org pseudo-package to send a *source* debdiff,
rationale and associated bug numbers to the Stable Release Managers, and
await a request to upload or further information.
If you are confident that the upload will be accepted without changes,
please feel free to upload at the same time as filing the
release.debian.org bug. However if you are new to the process, we would
recommend getting approval before uploading so you get a chance to see
if your expectations align with ours.
Either way, there must be an accompanying bug for tracking, and your
upload must comply with the acceptance criteria below.
If you anticipate that your upload will be a candidate for stable-updates,
including a draft announcement text to be sent in your name is always
appreciated.
Update criteria
===============
Here's a reminder of our usual criteria for accepting fixes. These are
designed to help the process be as smooth and frustration-free as
possible for both you and us.
* The bug you want to fix in stable must be fixed in unstable
already (and not waiting in NEW or the delayed queue)
* The bug should be of severity "important" or higher
* Bug meta-data - particularly affected versions - must be
up to date
* Fixes must be minimal and relevant and include a sufficiently
detailed changelog entry
* A source debdiff of the proposed change must be included
in your request (not just the raw patches or "a debdiff
can be found at $URL")
* The proposed package must have a correct version number
(e.g. ...+deb10u1 for buster or +deb9u1 for stretch) and you
should be able to explain what testing it has had
* Fixes for security issues should be co-ordinated with the
Security Team, unless they have explicitly stated that they
will not issue an DSA for the bug (e.g. via a "no-dsa" marker
in the Security Tracker) [SECURITY-TRACKER]
Please don't post a message on the debian-release mailing list and
expect it not to get lost - there must be a bug report against
release.debian.org.
We make extensive use of usertags to sort and manage requests, so
unless you particularly enjoy crafting bug meta-data, reportbug is
generally the best way of generating your request. Incorrectly tagged
reports may take longer to be noticed and processed.
[BTS] https://bugs.debian.org/release.debian.org
[QV] https://release.debian.org/proposed-updates/stable.html
[SUA] https://lists.debian.org/debian-devel-announce/2011/03/msg00010.html
[SECURITY-TRACKER] https://security-tracker.debian.org/
Thanks,
For the SRMs:
--
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