Firefox/privacyandsecurity: Difference between revisions
< Firefox
Jump to navigation
Jump to search
| Line 71: | Line 71: | ||
<p> </p> | <p> </p> | ||
* '''Duration:''' Tuesday July 5 - Monday July 18 | * '''Duration:''' Tuesday July 5 - Monday July 18 | ||
* '''Iteration Backlog:''' [https://mzl.la/ | * '''Iteration Backlog:''' [https://mzl.la/29zOcjd View in Bugzilla] | ||
* '''Dashboard:''' [https://docs.google.com/a/mozilla.com/spreadsheets/d/155k3Ja06QVgRj9F_DnAJxC8wfH_lWM4N9eZal4llefk/edit?usp=sharing View Priority List] | * '''Dashboard:''' [https://docs.google.com/a/mozilla.com/spreadsheets/d/155k3Ja06QVgRj9F_DnAJxC8wfH_lWM4N9eZal4llefk/edit?usp=sharing View Priority List] | ||
* '''Completion Goal:''' | * '''Completion Goal:''' 0 work items. | ||
<p> </p> | <p> </p> | ||
<bugzilla> | <bugzilla> | ||
Revision as of 14:48, 8 July 2016
Firefox Desktop Privacy and Security Team
Releases
Current Release - 50
- Duration: Tuesday June 7 - Monday July 18
- Iteration 50.1: Tuesday June 7 - Monday June 20
- Iteration 50.2: Tuesday June 21 - Monday July 4
- Iteration 50.3: Tuesday July 5 - Monday July 18
- Iteration 50.4: Tuesday July 19 - Monday August 1
- Dashboard: View Priority List
- Release Goal: 6 work items
- Current Status - Updated Every Tuesday: View June 21 Update
52 Total; 0 Open (0%); 16 Resolved (30.77%); 36 Verified (69.23%);
Completed Releases
Upcoming Releases
Release plan when each Firefox version goes to Central, Aurora, Beta, & Release: View Rapid Release Schedule
Firefox 51 Release - Q3-2016
- Iteration 51.1: Tuesday August 2 - Monday August 15
- Iteration 51.2: Tuesday August 16 - Monday August 29
- Iteration 51.3: Tuesday August 30 - Monday September 12
Firefox 52 Release - Q3-2016/Q4-2016
- Iteration 52.1: Tuesday September 13 - Monday September 26
- Iteration 52.2: Tuesday September 27 - Monday October 10
- Iteration 52.3: Tuesday October 11 - Monday October 24
- Iteration 52.4: Tuesday October 25 - Monday November 7
Firefox 53 Release - Q4-2016/Q1-2017
- Iteration 53.1: Tuesday November 8 - Monday November 21
- Iteration 53.2: Tuesday November 22 - Monday December 5
- Iteration 53.3: Tuesday December 6 - Monday December 19
- Iteration 53.4: Tuesday December 20 - Monday January 2
- Iteration 53.5: Tuesday January 3 - Monday January 16
- Iteration 53.6: Tuesday January 17 - Monday January 23 (1-Week Iteration)
Iterations
Current Iteration - 50.3
- Duration: Tuesday July 5 - Monday July 18
- Iteration Backlog: View in Bugzilla
- Dashboard: View Priority List
- Completion Goal: 0 work items.
| ID | Summary | Status | Assigned to | Fx iteration |
|---|---|---|---|---|
| 1204007 | Cross out permission icons in the control center when they have been blocked | VERIFIED | gasolin@mozilla.com | 50.3 - Jul 18 |
| 1206252 | Display icons for blocked permission in the identity block | VERIFIED | Johann Hofmann [:johannh] | 50.3 - Jul 18 |
| 1267617 | Move notification anchors to the identity block | VERIFIED | Johann Hofmann [:johannh] | 50.3 - Jul 18 |
| 1269820 | Remove green lock with grey triangle when Mixed Active Content is Blocked | VERIFIED | Sebastin Santy [:seban] | 50.3 - Jul 18 |
| 1275896 | Replace hard-coded support link for SEC_ERROR_UNKNOWN_ISSUER | RESOLVED | Sebastin Santy [:seban] | 50.3 - Jul 18 |
| 1282455 | Use dedicated "Learn more..." link on time related cert error pages | VERIFIED | Sebastin Santy [:seban] | 50.3 - Jul 18 |
6 Total; 0 Open (0%); 1 Resolved (16.67%); 5 Verified (83.33%);
Meetings
Planning
| Day of week | Pacific Time | Eastern Time | Central European Time |
|---|---|---|---|
| Tuesdays | 8:00AM - 10:00AM | 11:00AM - 1:00PM | 5:00PM - 7:00PM |
- Frequency: One meeting per week on Tuesday.
- Duration: 2 hours
- Vidyo Room: FXPrivacy
- IRC: #secboston
Status Update
| Day of week | Pacific Time | Eastern Time | Central European Time |
|---|---|---|---|
| Monday, Wednesday, Thursday, Friday | 8:00AM - 8:30AM | 11:00PM - 11:30AM | 5:00PM - 5:30PM |
- Frequency: Four meetings per week on Monday, Wednesday, Thursday, Friday
- Duration: 30 min
- Vidyo Room: FXPrivacy
- IRC: #secboston
Prioritization
- P1: Must Have - development occurring in the current release.
- P2: Should Have - targeted for the current release if production capacity exists.
- P3: Could Have - planned for development in an upcoming release.
- P4: Will Have - not scheduled for any particular release.
- -- : No Priority Set - tracking for completion only.
Bugzilla
Queries
Release Backlog
Collection of priority work the team has committed to complete over the course of an entire release:
Iteration Backlog
Collection of priority work the team has committed to complete on in a two-week iteration:
Product Backlog
Collection of priority work related to the ongoing development and maintenance of the Firefox Desktop Privacy & Security features:
- All User Stories - View in Bugzilla
- All Work Bugs - View in Bugzilla
- 'P1' Bugs - View in Bugzilla - Must Have - development occurring in the current release.
- 'P2' Bugs - View in Bugzilla - Should Have - targeted for the current release if production capacity exists.
- 'P3' Bugs - View in Bugzilla - Could Have - planned for development in an upcoming release.
- 'P4' Bugs - View in Bugzilla - Will Have - not scheduled for any particular release.
- '--' Bugs - View in Bugzilla - No Priority Set - tracking for completion only.
Triage
Collection of work waiting for the team to review and determine if it should be included in the Product Backlog:
Bug Modifications - Team Members
Selecting a New Bug for the Current Iteration
- Select any 'P1' bug which is currently unassigned and not blocked on a dependency. If no 'P1' bugs are available then select from the available 'P2' bugs, and so on.
- Add the following if not already present:
- [fxprivacy] whiteboard tag.
- current iteration flag.
- QE verification flag.
Adding a New Bug to the Product Backlog
- Add the [fxprivacy] whiteboard tag.
- Set the bug as a dependency of the user story bug if applicable.
- The bug priority will be set during the Planning Meeting:
- 'P1': Must Have - development occurring in the current release.
- 'P2': Should Have - targeted for the current release if production capacity exists.
- 'P3': Could Have - planned for development in an upcoming release.
- 'P4': Will Have - not scheduled for any particular release.
- '--': No Priority Set - tracking for completion only.
Adding a New User Story Bug to the Product Backlog
- Add the [fxprivacy] whiteboard tag.
- Add the [userstory] whiteboard tag.
- Add work bugs related to the completion of the user story as dependencies.
- Do not add the Iteration flag.
Submitting a Bug for Triage
- Add the [triage] whiteboard tag.
- Add the [fxprivacy] whiteboard tag.
Contributing
If you encounter an issue please use this Bugzilla template link for filing a new bug.