MDN/Development/Meetings/Triage: Difference between revisions
< MDN | Development | Meetings
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
## Select <i>Change several bugs at once</i> | ## Select <i>Change several bugs at once</i> | ||
## Select all new security bugs | ## Select all new security bugs | ||
## In the <i>CC</i> field, add the email addresses of all MDN staff | ## In the <i>CC</i> field, add the email addresses of all MDN staff | ||
## Click <i>Commit</i> | ## Click <i>Commit</i> | ||
# Plan major bugs from Friday's [https://etherpad.mozilla.org/mdn-bug-triage New Bug Triage] | # Plan major bugs from Friday's [https://etherpad.mozilla.org/mdn-bug-triage New Bug Triage] | ||
Latest revision as of 17:12, 14 August 2014
Combines our old Pull Request Triage meetings and Bug triage:
| Max Time: | 30m |
| Required Attendees | MDN devs |
| Optional Attendees | MDN stake-holders |
| Outcomes |
|
During the PR portion we:
- Open our Github Pull Request Triage tool
- Starting with the oldest, for each pull request not updated within the last 24 hours:
- Submitter briefly describes pull request
- Assignee gives update on the status
- Team decides to either:
- Update and keep the pull request active
- Close the pull request
During the bug triage we:
- Check for any new security bugs
- Pull up the list of security bugs
- Select Change several bugs at once
- Select all new security bugs
- In the CC field, add the email addresses of all MDN staff
- Click Commit
- Plan major bugs from Friday's New Bug Triage