On Fri, 15 Aug 2025 20:50:48 +0100, Colin Watson <cjwat...@debian.org> wrote: >This is a matter of my professional judgement, and the answer won't >always be the same kind of thing. When we're coming up to a release, I >tend to focus almost entirely on RC bugs. Near the start of a release >cycle, my current judgement is that the most useful thing I can do is to >try to reduce our backlog of new upstream releases. These days most of >my time is spent on the Python team, where we currently have 803 >packages that are out of date relative to upstream; to me that's a >shockingly high number. All of those represent contributions that have >been made and have not yet got into Debian, just as MRs do; I don't >necessarily consider MRs to be a higher priority just because they're in >Salsa. Because upstream Python packaging is such a complex landscape, >some of them are tricky to integrate and need somebody quite >experienced.
Thank you for this insight in your work, this was very interesting. And it prompts a question: Integrating a new upstream release means changing at least two, in the case of pristine-tar being used three branches at once, tightly connected to each other, and possibily an external file (the orig tarball). Could a contributor do that with an MR? Greetings Marc -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402
