@Oliver contentious bugs in high volume projects/packages suffer when
a bug looks superficially like a users symptoms and they say 'hey,
this has regressed' - e.g., 'black screen on boot' : yet there can be
hundreds of discrete causes causing that symptom.
Is it unreasonable to have a team as bug supervisor if you want to
allow a wide spread of developers to do anything with bugs. Note too
that the original bug *filer* will be able to un-release a bug : after
all they are the person with the original symptoms.
@Oliver contentious bugs in high volume projects/packages suffer when
a bug looks superficially like a users symptoms and they say 'hey,
this has regressed' - e.g., 'black screen on boot' : yet there can be
hundreds of discrete causes causing that symptom.
Is it unreasonable to have a team as bug supervisor if you want to
allow a wide spread of developers to do anything with bugs. Note too
that the original bug *filer* will be able to un-release a bug : after
all they are the person with the original symptoms.