On Fri, 2007-04-20 at 17:33 -0600, Ryan Hill wrote: > Or even just some way > to differentiate CCed archs from CCed randompeoples.
You probably need to "emerge eyeballs" and enable them with the "look" command. After the look command gets the input, you'll need to parse it with the "think" subroutine, and that should tell you quite quickly whether the CC list includes any architecture teams or not. *grin* Seriously, this has worked for the arch teams quite well up until now. I really don't see the need to change things. Doing the reassignment doesn't really gain us anything. In my case, it usually makes things harder on me, since I many times simply look at CC to see what arches still need to do something. The worst offenders are the bugs that are assigned to one arch and still have other arches listed on CC. Personally, I like the "assign to maintainer, CC arches" approach and see no reason to reassign anything, even if there is just one architecture left. Of course, I think the maintainer should be assigned *any* bug that involves their package, even when it is just a keyword request. As others have stated, there's many times when there might be a problem with the package the maintainer needs notification on, and I've stated that I've seen a few recent stabilization requests for packages that shouldn't have been stabilized/keyworded. Were I not on a couple arch teams, I never would have even known that someone requested the package get keyword changes. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
