Firefox/Aurora/2011-04-28: Difference between revisions
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
===Status of AUS work for updating channel changer=== | ===Status of AUS work for updating channel changer=== | ||
* Tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=648087 bug 648087] | * Tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=648087 bug 648087] and [https://bugzilla.mozilla.org/show_bug.cgi?id=653312 653312] | ||
* Work has been completed. | * Work has been completed. | ||
Revision as of 21:14, 28 April 2011
Agenda
- Aurora meeting schedule.
- Plan for security bug triage and nominations.
- Plan for increasing user base on Beta and Aurora channels.
- Status of Beta build
- Status of AUS work for updating the channel changer.
- Communications.
- Bug triage.
Notes
Aurora meeting schedule
- No changes. Meetings will be at 2:00pm PDT on Tues and Thurs.
Plan for security bug triage and nominations
- The security team will be responsible for triaging all tracking? and tracking+ *security* bugs and monitoring their progress. They obviously have the best information about these bugs and set the security rating.
- In some cases the security team may go ahead and simply set tracking+ without even nominating it.
- This triage along with monitoring the progress will happen during the weekly critsmash meeting.
- This largely means that the Aurora triage team will skip over these *tracking* bugs during their triage sessions. They still may ping the security team about a particular bug if they see something that hasn't made progress.
- The Aurora triage team will be responsible for approving the patches for the security bugs as part of their regular triage process.
Plan for increasing user base on Beta and Aurora channels
- Tracked in bug 651982
Status of Beta build
- Tracked in bug 652641
Status of AUS work for updating channel changer
- Tracked in bug 648087 and 653312
- Work has been completed.