On 11/04/2010 07:47 PM, Matt McCutchen wrote:
If someone else cares and retests, they ideally
would be able to reopen it, but Bugzilla currently doesn't allow that
Somebody can correct me if I'm wrong but as I recall we changed that
( should be a discussion about this in this list archives or on the test
list archives or QA meetings log even )
If I can recall correctly the problem was that the ( new/inexperienced
) reporters were constantly opening bugs maintainer(s) closed due to
misunderstanding of the underlying problem or simply disagreement
between them and they were constantly changing severity and priority of
bugs which maintainers use to prioritise their own work flow .
( new/inexperienced reporters had a tendency to think the bug they
experienced was the most severe one )
Conscious was reached to strip those rights from the reporters and
triagers by default and if/when they joined certain fas group(s) they
would gain that access.
This move generally improved interaction between reporters/triagers and
maintainers/packagers and so far you are the only one I've noticed that
mentions the lack of the ability to do this in our bugzilla.
I think the general practice between reporters is to file a new report
and mentioning regression and refer to the old bug in that report since
commenting on a closed bug may not have the ( current ) maintainer(s)
still subscribed to it.
Maintainers themselves can then decide if they want to reopen the old
one and mark the new one as duplicate or keep it a separated bug.
Dont hesitate to correct me if memory has been playing tricks on me
and this discussion and relevant action never took place this is all
very vague to me.. .