Hi, On 20/08/24 at 07:28 +0200, Helmut Grohne wrote: > There are various QA-related teams looking at packages from other > maintainers. When it trips a check, that often incurs time from some QA > person investigating a report or failure. Examples: > * Lucas Nussbaum, Santiago Vila and a few more regularly perform > archive rebuilds and report failures. They review a significant > fraction of reports before sending, but there also is CPU resources > for performing all those builds involved.
FWIW, I exclude packages that are not in testing when performing archive rebuilds. > When to remove a package? > > [...] > > Human readable explanation: > * Packages in sid > * not in bookworm or trixie > * not a key package > * affected by an RC bug that has been last modified more than a year ago > * not among a few selected exceptions This looks good to me. Maybe we could also reduce the cost of removals for users and potential new maintainers, by improving the information provided in various places on how to get the latest source and binary packages that were in Debian (pointing to snapshot.debian.org). Things to look at: - messages sent to the BTS when closing bugs for removed packages - tracker.debian.org Lucas
