128
edits
QA/Bug Triage Guidelines: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 66: | Line 66: | ||
| Mozilla Communication || When there is a lot of Mozilla Communication within the bug, ping a developer on IRC and ask him to set the appropriate component | | Mozilla Communication || When there is a lot of Mozilla Communication within the bug, ping a developer on IRC and ask him to set the appropriate component | ||
|- | |- | ||
| Close Me <date> || Apply at your comfort, there is no standard. If you apply it, please give the reporter a chance to respond ( | | Close Me <date> || Apply at your comfort, there is no standard. If you apply it, please give the reporter a chance to respond (two weeks) | ||
|- | |- | ||
| Enhancement & Feature Requests || Enhancements and Feature Requests should have an appropriate Component assigned. The developers and PM in that component will decide if it will be implemented or marked as Resolved-Won't Fix | | Enhancement & Feature Requests || Enhancements and Feature Requests should have an appropriate Component assigned. The developers and PM in that component will decide if it will be implemented or marked as Resolved-Won't Fix | ||