On Thu, 1 Aug 2024 07:53:39 +0200 Niels Thykier <ni...@thykier.net> wrote:
Package: release.debian.org
Severity: wishlist
X-Debbugs-Cc: ni...@thykier.net
Hi,
The emails from the auto-remover triggers people to ask questions like
"how do I prevent the auto-removal?" (usually on d-release or
d-mentors). It seems to me that the emails could serve the relevant
documentation (or a link to it) and thereby hopefully reduce the number
of times the question(s) get raised.
Best regards,
Niels
Examples could include:
* How do I prevent removal?
(Triage the bug and ensure metadata is correct, Fix or downgrade
the bug, ensure timely migration. Periodic updates to the RC bug
if those items are stalled)
* What do I do when the RC bug is not in my package?
(Provide patches, check if the dependency could do with a
co-maintainer or need to be salvaged, etc.)
* What are the timelines for removals?
X days from the bug first appears this removal notice is sent out.
Then after Y since the last update to the bug, the auto-removal kicks
in.
Note: These timelines only apply to automatic removals. The release
team can remove packages manually earlier than these timelines if
they see the need for it. This another reason why it is good to
document progress on the bug even if it does not translate directly
into a bug being fixed here and now as that makes the release team
aware that you are working on a fix.
* What happens if my package is auto-removed from testing?
It will be removed from testing. Outside of freezes, this is usually
less of a problem, since as soon as the bug and any other testing
blockers have been resolved, it can migrate back.
For freezes, it is important to stay diligent and resolve these
issues in a timely manner. Depending on the stage of the freeze, the
package might not be able to re-enter testing once removed.
Best regards,
Niels
