1 |
> |
2 |
> I think this is an excellent idea. I wrote an automated trouble |
3 |
> ticketing system years ago for the mainframe and it's an excellent way |
4 |
> to get quality information into the system. The one drawback was that |
5 |
> we ended up having a lot more bugs entered into the system. Once you |
6 |
> have the shell it wouldn't be hard to hook it into batch processes and |
7 |
> have emerge automatically send bug reports when it fails. When this |
8 |
> happens you end up with multiple, identical bug reports because users |
9 |
> tend to re-create the error a few times before they head to the forums |
10 |
> or bugzilla for help. On the plus side it would be much easier to find |
11 |
> duplicate bugs since the titles would be uniform. |
12 |
> Glide |
13 |
|
14 |
If people are automating I'd prefer they not post bugs directly on |
15 |
bugzilla. When we do tinderboxing and whatnot we generally generate a |
16 |
standalone set of data to act on, as a human eye and processing can spot |
17 |
invalid problems as well as duplicates. |
18 |
|
19 |
-- |
20 |
gentoo-dev@g.o mailing list |