On Tue, 2005-05-24 at 14:44 -0600, R Hill wrote: > > The most productive thing you could do, would be to figure out a simple > > way of testing ebuilds, marking them as tested, and assigning them to > > the proper parties quicker than is being done now. > > I like this. It could probably be done through keywording, and in fact > the keywords are already there (ebuild and tested)[1]. They just never > get used. ;) Maybe raising people's (user's) awareness of their > existence and how to use them properly would help. I'd be willing to > write up a Bugzilla user-guide if there's any interest in it; I've been > meaning to write one for the wiki/forum anyways. > > As for what happens after a ebuild is tested, I see a couple options. > Devs can always just keep doing what they do now and just use the tested > keyword as a handy at-a-glance reference. Or, you could implement the > Bugzilla request system[2][3] to allow a tester to flag a bug ready for > review by a developer. I think this would both improve the turn-around > time on bumps and save some time for the devs by letting them know that > any such request both has an ebuild attached and that ebuild has been > tested by the community. Adding a review request flag does add a little > more complexity to the process of using bugzilla, but with proper user > documentation I think the benefit will outweigh the cost. > > > What we really need is to have the AT program extended from just amd64 > > to every arch, including x86 (which desperately needs an arch team). > > Really? What does such a team do?
They do exactly what is said above. They test ebuilds that are submitted. They also test patches and just about anything else that goes into bugzilla. Basically, they are a group of people that own a certain architecture that are willing to possibly destroy their machines in the name of the greater good of QA and Gentoo. In fact, a good number of the amd64 arch testers have started to become developers, so it is a good path into development, as the AT is very familiar with our practices and has already demonstrated his abilities. -- Chris Gianelloni Release Engineering - Strategic Lead/QA Manager Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
