Re: QA Experiment: removing "stale uploaders"
Hi,
This is a very reasonable thing to do considering the policy change. I also have two packages where I mistakenly ended up as the maintaner and DPT as uploader (see python-graphene-directives and python-graphene-federation) because of tooling defaults and me missing to see it in the end. I have been contemplating since I realized this about how urgently I should take care of this. What I mean is that, does this call for an immediate revision of the debian package, or is it sufficient to have a git commit to reverse it and then later upload it with the next possible upstream release. Thoughts?
PS: And depending on how strictly we want to enforce this, there can perhaps also be a lintian warning/error?
Best,
Ananthu
On 15 August 2024 8:45:24 pm UTC, "Louis-Philippe Véronneau" <pollo@debian.org> wrote:
>5. Some of the packages flagged as "Debian Python Team" have the team as Uploaders. Considering the recent policy change, we should probably try to make things more uniform by having the DPT as maintainer everywhere.
Reply to: