Re: Bumping bugs to rc-severity
Le Thu, Nov 13, 2025 at 06:22:46PM +0100, Helmut Grohne a écrit :
> Hello fellow developers,
>
> On Sat, May 31, 2025 at 10:07:07PM +0200, Helmut Grohne wrote:
> > All of the bugs are usertagged with a number of tags sharing a
> > "libcrypt-" prefix:
> >
> > https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=helmutg@debian.org
> >
> > At the time of this writing, there are 233 remaining bugs.
>
> In the mean time, we released trixie and are down to 142 bugs. As we
> would like to complete this transition in a timely manner, I consulted
> with the release team and am now bumping the remaining bug reports to RC
> severity.
[[On the practice of bumping severity to RC]]
The issue is that from the point of view of the maintainer this is a
fresh RC bug, while from the point of view of dak this is an old RC bug
that warrant removal from testing.
In particular, one might want to NMU a package to prevent a reverse
dependency to be removed from testing only to realize the RC bug is less
than two days old and doing an NMU straight away feel a bit
heavy-handed.
Any best practice to follow ?
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: