| 1 |
On Friday 29 February 2008 13:13:16 Richard Freeman wrote: |
| 2 |
> Rémi Cardona wrote: |
| 3 |
> > +1 on that idea, using bugzilla with an external tool for keyword |
| 4 |
> > requests is a good idea. |
| 5 |
> > |
| 6 |
> > The tool could do bugzilla research to see if the keyword has already |
| 7 |
> > been requested and point the user to the corresponding bug report, |
| 8 |
> > hopefully limiting the number of dupes. |
| 9 |
> |
| 10 |
> ++ |
| 11 |
> |
| 12 |
> It would still be nice to have better status tracking in bugzilla - some |
| 13 |
> way for ATs to officially mark that stuff is tested in a way that can be |
| 14 |
> easily queried (so that ATs can find stuff that isn't tested, and devs |
| 15 |
> can find stuff that has been). The issue about hard-to-test packages is |
| 16 |
> really a separate one, but one that could use a solution... |
| 17 |
|
| 18 |
Definitely. I find it very annoying searching through bugzilla looking for |
| 19 |
things that other Arch Testers haven't tested. On the other hand, after a |
| 20 |
while you start to remember which bugs haven't been tested(at least if you |
| 21 |
are on an arch with >150 bugs). Barring that case, such a system would be |
| 22 |
very nice. |
Archives