Am Sat, Mar 14, 2026 at 06:39:42PM +0100 schrieb Ludovic Courtès: > Andreas Enge <[email protected]> skribis: > > This is certainly an important point to discuss, and something where > > consensus must be reached. I could live with anything that does not > > lengthen the current delays, that is, keeps it possible to remove > > packages within one month. > Yeah, I would tend to keep it at one month, in the hope it gives more > time for people to notice and propose a fix (which I think is less > likely to happen once the package has already been removed, though I > don’t have any stats!).
Well, I iterate that for me, the shorter, the better :) Just a few days ago I have once again filed a second removal request for something that I had forgotten was on the list... Some people (before the submission offline, and also on the Codeberg issue) have pointed out that a unique timeline would make things easier. So maybe a compromise would be to set everything at 2 weeks for the initial deprecation issue, and 1 week as in the proposal for the pull request, for a total of 3 weeks? Input from the channels would be good! > But then I agree we must also make it easy for the “package janitors” to > easily navigate the list of pending removals. Did you find that setting > a target date in Codeberg issues helps with this? Yes, this is precisely how I work: click on the red "deprecation" label in one of the issues on the first page, go towards the end and work on those that are on or after the due date. So the state is on Codeberg and does not have to be in our heads :-) Andreas
