Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: gentoo-dev@l.g.o, wg-stable@g.o, arch-leads@g.o, alpha@g.o, amd64@g.o, amd64-fbsd@g.o, arm@g.o, arm64@g.o, hppa@g.o, ia64@g.o, m68k@g.o, mips@g.o, ppc@g.o, ppc64@g.o, s390@g.o, sh@g.o, sparc@g.o, x86@g.o, x86-fbsd@g.o
Subject: [gentoo-dev] Re: [RFC] Future of gentoo's stable and unstable trees: what are your thoughts?
Date: Mon, 24 Jul 2017 21:52:48
Message-Id: 1500933148.4544.68.camel@gentoo.org
In Reply to: [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? by Sergei Trofimovich
1 El lun, 24-07-2017 a las 22:22 +0100, Sergei Trofimovich escribió:
2 > 4. Q: How to push more packages into STABLE?
3 >
4 >    A: File automatic STABLEREQ bugs more aggressively if no known bugs
5 >       exist for a package version. The rough workflow is the following:
6 >
7 >       - Grab a list of candidates for stabilization (will need
8 >         additional tooling)
9 >       - File STABLEREQ against maintainer only first.
10 >       - Maintainer will have a 2-week timeout to either proceed with
11 >         request:
12 >         - add "runtime testing required fields", CC relevant arches to
13 >           start stabilization
14 >         - or set blocking bugs against STABLEREQ to stop stabilization
15 >       - After 2-week timeout tooling automatically CCes arches and
16 >         stabilization happens (ideally with minimal manual work)
17 >       - Profit!
18
19 I think the tools for this were already developed... but they were relying on
20 some of us remembering to run them from time to time :/
21 https://gitweb.gentoo.org/proj/arch-tools.git/tree/file-stabilization-bugs.py
22 https://gitweb.gentoo.org/proj/arch-tools.git/tree/maintainer-timeout.py
23 https://gitweb.gentoo.org/proj/arch-tools.git/tree/stabilization-candidates.py
24
25 Thanks specially for sharing https://wiki.gentoo.org/wiki/Package_testing#Tools
26 link, it summarizes all the process really well :O
27
28 Also, it seems that tatt-9999 is able to do most of the work... then only thing
29 that maybe has no official script to get it, for example, what would be the best
30 way of getting the list of bug numbers that are pending to handle?
31
32 For example, if I go to the list manually and pick 10 random bugs, it's ok to
33 run tatt and copy&paste every bug number but, if the arch queue has 300 pending
34 bugs. Do we have a way to simply get a plain text with all the bug numbers from
35 bugzilla interface? Having links per arch pointing to that list of bugs with
36 arches CCed and sanity-check=+ would be probably helpful ;)
37
38 Thanks