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