Hi team, Sorry for the subject, this mail is more like questions than given ideas :-).
After reading the DPL's contact and its responses, it got me thinking - and this is also a personal feeling - that the DPT is a place where I can seek help. This is beneficial because we understand that if we encounter a Debian packaging issue specific to Python, we can expect a prompt response from experienced people within the team. However, it's true that each one maintains their own packages, while some others fix RC bugs. But IMHO we lack like clear direction to follow as a team. While ultimately, we just need to ensure that the packages under the DPT umbrella are up-to-date with upstream and free of RC bugs as much as possible. I don't know if that 'direction' is needed. I understand that our team's priority is to address 3.12 bugs [0], as mentioned in the irc topic. I know that some people are already working on this, and they don't necessarily need to seek permission before tackling an RC bug. However, perhaps we could attempt to organize our efforts better. Maybe we could identify packages that are candidates for removal like [1] and try to reduce the list of RC bugs. Another question is: what should we do with packages that are not under the team's umbrella but are affecting Python 3.12? On the other hand, we could assess if there are any improvements needed in our tools, such as pybuild, or determine which packages require, for instance, autopkgtests, lintian, etc. Or maybe we can start making short IRC meetings once a week or every two weeks? Experienced members of the team, do you think this is feasible given the DPT workflow? I would like to hear the opinion from the team :-) [0] https://deb.li/3T4QN [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025181 cheers, Emmanuel Arias ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ eam...@debian.org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: FA9DEC5DE11C63F1 ⠈⠳⣄
