Gentoo Archives: gentoo-dev

From: Tom Wijsman <TomWij@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] robo-stable bugs
Date: Mon, 20 May 2013 18:31:20
Message-Id: 20130520202919.6630d3f8@TOMWIJ-GENTOO
In Reply to: Re: [gentoo-dev] robo-stable bugs by "Robin H. Johnson"
1 On Mon, 20 May 2013 18:00:49 +0000
2 "Robin H. Johnson" <robbat2@g.o> wrote:
3
4 > http://www.gossamer-threads.com/lists/gentoo/dev/173889?do=post_view_threaded
5 > The thread does mention that atoms should be first, as well.
6 > It also makes sorting and viewing much easier (all related atoms are
7 > together).
8
9 Thanks.
10
11 > > > Also, your script does not set the STABLEREQ keyword. People are
12 > > > having to hunt down your robo-stabilisation requests and add it
13 > > > themselves. You should just do it yourself or turn your script
14 > > > off.
15 > > Maintainer(s) and arch team member(s) blamed me for setting this. :(
16 > I think the keyword should be there.
17 >
18 > If anybody else things the keyword should NOT be there, I'd like to
19 > hear from them here.
20
21 From what I heard, this keyword is used to see whether a stabilization
22 request bug is an actual stabilization request. Adding the keyword
23 without CC-ing arches clutters the bug list that tracks all stabilazion
24 request bugs since there would then be bugs that the arches can not
25 take any action on.
26
27 Of course arches use the CC feature for tracking these, but there are
28 persons tracking the entire list too to pay attention to bugs that have
29 been forgotten about; or persons whom have access to multiple arches
30 and are in multiple arch teams may also prefer to use the full list
31 instead of depending on the individual CC mails.
32
33 But that's just my limited view on this, the relevant maintainers and
34 arch team members that request this can probably shed a better light on
35 the need for STABLEREQ to only be placed by the maintainer and not by
36 the reporter or bug wrangler.
37
38 > Additionally, there used to be an old webapp where you could select by
39 > dev/herd and see how many days every package with that dev/herd had
40 > been in ~arch for all given arches. Something like that easily usable
41 > would be handy again, as a stop-gap to automatic stabilization.
42
43 We have `iamlate` for this in app-portage/gentoolkit-dev.
44
45 --
46 With kind regards,
47
48 Tom Wijsman (TomWij)
49 Gentoo Developer
50
51 E-mail address : TomWij@g.o
52 GPG Public Key : 6D34E57D
53 GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] robo-stable bugs Michael Weber <xmw@g.o>