canmove, Confirmed users
1,953
edits
(→Planning Sprints: Add how long a sprint is) |
(→Triaging Requests: Added link to content issue triage process article, and updated description of how DDNs are handled) |
||
Line 30: | Line 30: | ||
* [https://mzl.la/MDNBugs Requests for changes to the MDN platform] (product="developer.mozilla.org") | * [https://mzl.la/MDNBugs Requests for changes to the MDN platform] (product="developer.mozilla.org") | ||
For the first type of request, see the [[Engagement/MDN_Durable_Team/Processes/Content_issue_triage_process|content issue triage process]]. | |||
Bugs with "dev-doc-needed" are grouped based on the | Bugs with "dev-doc-needed" are grouped based on the web platform feature they pertain to. A User Story (or Epic) is created to address these "dev-doc-needed bugs" (often shortened to "DDN bugs" or even "DDNs") for each web platform feature, and is scheduled in order to be ready when that feature is available in multiple browsers. | ||
The third category of requests is triaged in a weekly "Bug Swat" meeting. See [https://public.etherpad-mozilla.org/p/mdn-bug-triage MDN Bug Triage Guidelines] for details. See the [[MDN/Meetings]] page for details about triage meetings, and the [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 Public MDN Events calendar] for their schedule. | The third category of requests is triaged in a weekly "Bug Swat" meeting. See [https://public.etherpad-mozilla.org/p/mdn-bug-triage MDN Bug Triage Guidelines] for details. See the [[MDN/Meetings]] page for details about triage meetings, and the [https://calendar.google.com/calendar/embed?src=mozilla.com_2d35383434313235392d323530@resource.calendar.google.com&ctz=GMT&pli=1 Public MDN Events calendar] for their schedule. |