El lun, 24-07-2017 a las 22:22 +0100, Sergei Trofimovich escribió: > 4. Q: How to push more packages into STABLE? > > A: File automatic STABLEREQ bugs more aggressively if no known bugs > exist for a package version. The rough workflow is the following: > > - Grab a list of candidates for stabilization (will need > additional tooling) > - File STABLEREQ against maintainer only first. > - Maintainer will have a 2-week timeout to either proceed with > request: > - add "runtime testing required fields", CC relevant arches to > start stabilization > - or set blocking bugs against STABLEREQ to stop stabilization > - After 2-week timeout tooling automatically CCes arches and > stabilization happens (ideally with minimal manual work) > - Profit!
I think the tools for this were already developed... but they were relying on some of us remembering to run them from time to time :/ https://gitweb.gentoo.org/proj/arch-tools.git/tree/file-stabilization-bugs.py https://gitweb.gentoo.org/proj/arch-tools.git/tree/maintainer-timeout.py https://gitweb.gentoo.org/proj/arch-tools.git/tree/stabilization-candidates.py Thanks specially for sharing https://wiki.gentoo.org/wiki/Package_testing#Tools link, it summarizes all the process really well :O Also, it seems that tatt-9999 is able to do most of the work... then only thing that maybe has no official script to get it, for example, what would be the best way of getting the list of bug numbers that are pending to handle? For example, if I go to the list manually and pick 10 random bugs, it's ok to run tatt and copy&paste every bug number but, if the arch queue has 300 pending bugs. Do we have a way to simply get a plain text with all the bug numbers from bugzilla interface? Having links per arch pointing to that list of bugs with arches CCed and sanity-check=+ would be probably helpful ;) Thanks
