¡Hola Salvo! El 2026-09-05 a las 22:34 +0200, Salvo Tomaselli escribió:
My quesion is, how do we track if they are still a problem or someone else in the team took care of it without a bug number?
Just some context, during the Python BoF in DebConf one of the topics was about Python 3.15, about to be released in October and aimed to be included in forky, I've done some follow up in [1], and been working to make all packages work with python 3.15. I've been ccing the list when sending a new bug submit as I considered that these were of interest to the list, I'll stop adding the cc to the list, the issues should still be visible in the bts by usertag or in the tracker for the packages that have the team tracker as maintainer.
Could it be better for them to have a low priority bug associated that could be raised later on?
They are mostly normal bugs for now, and they can be raised to serious when python3-defaults in sid add python 3.15 as the supported version. From Emmanuel Arias:
Anyway, +1 to have something to coordinate the team work, but not idea how.
The bts has a claim action, that can be used with bts claim, udd can be used to query the involved bugs and see who has claimed them [2]. Happy hacking, [1]: https://lists.debian.org/debian-python/2026/08/msg00065.html [2]: https://udd.debian.org/bugs/?release=any&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=python3.15&fusertaguser=debian-python%40lists.debian.org&allbugs=1&cseverity=1&cclaimed=1&sortby=id&sorto=asc&format=html#results -- "Can you imagine what I would do if I could do all I can?" -- Sun Tzu Saludos /\/\ /\ >< `/
signature.asc
Description: PGP signature
