John, I think we already had this conversation. Again, the link you
provide me with indicates that a Mozilla bug with an incomplete status
*MUST* additionally have one of a number of tags, none of which have
been applied to this bug report. I am perfectly willing to play by the
rules, but the Mozilla team should be following their own procedure.
Activities/Tags
(See MozillaTeam/Bugs/Tags for a detailed description on tags, their meaning as
well as typical actions associated with them)
* <none> - this is illegal, aka a triage bug: state need info always
needs one of the tags below. If there is a bug that does not fit, talk to us in
order to find a new one.
* For Crashers:
o mt-needreport - a useful crash report from the user is
needed.
o mt-needretrace - someone to do a retrace of the crash
report submitted in the bug is needed.
* For Feature Bugs:
o mt-needtestcase - a step by step description on how to
reproduce the problem is needed.
o mt-needtester - a tester is needed which can provide
responsive feedback at best in the IRC channel.
* All Bugs:
o likely-dup - bugs that are duplicates, but triager does
not have bug number of MASTER bug at hand, can be tagged 'likely-dup'. Other
triagers can then pick them, find MASTER bug and mark them appropriately.
o mt-needsummary - someone needed to clean up the issue
summary before proceeding.
o mt-confirm - this bug looks ready for "Confirmed".
Someone with experience is needed review and transition it to "Confirmed" if
this report is fine.
--
firefox grey
https://bugs.launchpad.net/bugs/184792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
