On Mon, 20 May 2013 18:00:49 +0000 "Robin H. Johnson" <robb...@gentoo.org> wrote:
> http://www.gossamer-threads.com/lists/gentoo/dev/173889?do=post_view_threaded > The thread does mention that atoms should be first, as well. > It also makes sorting and viewing much easier (all related atoms are > together). Thanks. > > > Also, your script does not set the STABLEREQ keyword. People are > > > having to hunt down your robo-stabilisation requests and add it > > > themselves. You should just do it yourself or turn your script > > > off. > > Maintainer(s) and arch team member(s) blamed me for setting this. :( > I think the keyword should be there. > > If anybody else things the keyword should NOT be there, I'd like to > hear from them here. From what I heard, this keyword is used to see whether a stabilization request bug is an actual stabilization request. Adding the keyword without CC-ing arches clutters the bug list that tracks all stabilazion request bugs since there would then be bugs that the arches can not take any action on. Of course arches use the CC feature for tracking these, but there are persons tracking the entire list too to pay attention to bugs that have been forgotten about; or persons whom have access to multiple arches and are in multiple arch teams may also prefer to use the full list instead of depending on the individual CC mails. But that's just my limited view on this, the relevant maintainers and arch team members that request this can probably shed a better light on the need for STABLEREQ to only be placed by the maintainer and not by the reporter or bug wrangler. > Additionally, there used to be an old webapp where you could select by > dev/herd and see how many days every package with that dev/herd had > been in ~arch for all given arches. Something like that easily usable > would be handy again, as a stop-gap to automatic stabilization. We have `iamlate` for this in app-portage/gentoolkit-dev. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
