Quoting Peter Green (2025-09-24 02:42:51) > On 24/09/2025 01:05, NoisyCoil wrote: > > So no, it's not automatically lost. But it can become due to high traffic, > > if no one does the things I listed. > > I can't speak for how others decide which bugs to work on. I tend to work > from a mixture of sources including recent posts to the pkg-rust-maintainers > mailing list (which receives all posts to rust team bug reports) and the udd > bugs list for the team, I do look at older bugs but I can only action so > many. Clogging up my personal inbox and the debian-rust list isn't going to > change that.
It might be helpful to be able to see which bugreports have not been lost, e.g. by tagging as confirmed or pending. > It might be useful if you could somehow document which update requests are > most important to you and/or which ones are most important to particular > packaging efforts. I have now trawled through all Rust packages that I maintain, and annotated the bugreports affecting them. I will try consistently do that from now on. I don't see how it is sensible to rank those bugreports - every bugreport requires maintenance of at least one patch, regardless of how "important" the change is from a user standpoint. With the "affects" annotation you get a glimpse of the burden the issue is causing, but only the tip of the iceberg: I also work on ~40 packages with binaries which are not yet in Debian, and the annotation does not show how often the patches need maintenance. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
