On 18/07/25 at 11:29 +0200, Didier 'OdyX' Raboud wrote:
> > The issues are very very very obviously not RC issues if they have
> > been there for 22 years without anyone noticing.
>
> Wrong: they are now, as per the Release Team decision. Sorry to repeat this,
> but a delegate has made an explicit request, with their delegate hat on,
> requesting the *-off packages to be removed from trixie / testing. You're of
> course entitled to disagree (and be pissed about it), but unless you manage
> to
> convince the Release Team otherwise, they are fully in the right to enforce
> their (DPL-delegated-powers') decision.
To be even more explicit, the release team delegation[1] states:
--------------------------------------------------------------->8
The Release Team oversees and manages the releases of the
testing, stable, and oldstable distributions (aka suites).
* Release Team members decide on the release schedule
(e.g. freeze dates, release dates for stable and point
releases for stable and oldstable).
* Release Team members define the content of the suites listed
above, that is:
- They define the packages that are part of those suites.
Generally, that is achieved by deciding:
- Which issues are release-critical (RC) (ie. making the
affected packages not suitable for stable releases)
usually by setting the corresponding bug's severity to
serious, grave or critical.
--------------------------------------------------------------->8
[1] https://lists.debian.org/debian-devel-announce/2020/07/msg00004.html
The same wording has been in place since 2013:
https://lists.debian.org/debian-devel-announce/2013/12/msg00007.html
If you want to override this release team decision, see Constitution[2],
4.1.3: https://www.debian.org/devel/constitution.en.html
Best,
Lucas
