|
Bugzilla – Full Text Bug Listing |
| Summary: | Bugzilla asks stupid things and doesn't ask important things | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | Alejandro Forero <bachue> |
| Component: | Bugzilla | Assignee: | E-mail List <novbugzilla-bugs> |
| Status: | VERIFIED WONTFIX | QA Contact: | Adrian Schröter <adrian.schroeter> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | aj, suse-beta |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Alejandro Forero
2005-12-16 20:46:46 UTC
Hello Alejandro, about the selection of a package: It wouldn't be too useful because the bug reporters often do not know which package really caused the error. This would lead to many miss-assignments and confusion. I for example initially check these bug reports and figure out who could take care of it. So it will reach the right person ;) AFAIK bugzilla would not even support this directly... and maintaining thousands of additional components also wouldn't be too handy. About the OS: Andreas: This might be the reason people tend to choose openSUSE instead of SUSE Linux, we should do something about this. (In reply to comment #1) > about the selection of a package: It wouldn't be too useful because the bug > reporters often do not know which package really caused the error. This would > lead to many miss-assignments and confusion. I for example initially check > these bug reports and figure out who could take care of it. So it will reach > the right person ;) AFAIK bugzilla would not even support this directly... and > maintaining thousands of additional components also wouldn't be too handy. Hmm, I tend to come from a Debian background, where bug reports are usually associated with specific packages. We, Debian users, tend to find this very useful. You can, for example, head to http://bugs.debian.org/runit, to see reports filled against the runit package. It is very useful, IMHO. I don't think the fact that not all bug reporters know the specific packages causing the bug is very important: if a bug is reported against the wrong package (or unknown), the package maintainer can always reassign it against the right package. That's like saying we shouldn't ask the severity because the reporter might report it incorrectly. I think that rather than assign bugs to specific *persons*, you should assign them to specific *packages*, where, obviously, they are automatically assigned to the package creator(s). I am aware that Bugzilla wouldn't support this directly, btw. I find it rather limited and poor for handling an entire GNU/Linux distribution, specially when compared with flexible and advanced bug trackers custom-made for this purpose (such as the Debian BTS). Perhaps we should begin to extend it and improve it (or drop it and use something better?) rather than live with its limitations? (In reply to comment #1) > about the selection of a package: [...] > AFAIK bugzilla would not even support this directly... The "good old" bugzilla.suse.de had this feature :-) > maintaining thousands of additional components also wouldn't be too handy. Quoting Adrian Schroeter: I will hand over the release job to Mr. Bash, he is more reliable :/ ;-) Bugzilla team, what do you think? (In reply to comment #3) > (In reply to comment #1) > > about the selection of a package: [...] > > AFAIK bugzilla would not even support this directly... > > The "good old" bugzilla.suse.de had this feature :-) How so? It would have had to use components for packages, either that or products. And if there are 1000+ packages I think that would be an administrative nightmare if each were mapped to a separate component in each product version. But that is a decision the package maintainers have to make. > > > maintaining thousands of additional components also wouldn't be too handy. I think that is your answer ;-) The OS field is used by many other products besides Suse 10. And unfortunately we have no way of customizing an OS list on a product by product basis. Only fill it out if it makes sense (i.e. you are loggin bugs on multiple OS's such as SLES and SUSE 10), otherwise the product already contains the information you need to know. This bug report discusses two issues: 1) The OS field is indeed redundant if the product *is* an OS. However, many of Novell's products are not operating systems, and the OS field is therefore relevant and cannot (usually) be derived or guessed from the product field. 2) Each product team decides how many bugzilla components they wish to manage -- this is not a decision by the bugzilla engineering team. Closing this bug. The SUSE Linux team might want to revisit issue 2. The bugzilla engineering team does not plan to revisit issue 1. |