Firefox/privacyandsecurity
From MozillaWiki
< Firefox
Contents
Firefox Desktop Privacy and Security Team
Releases
Current Release - 52
- Duration: Tuesday August 2 - Monday July 18
- Iteration 52.1: Tuesday Sept 21 - Monday Oct 3
- Iteration 52.2: Tuesday Oct 4 - Monday Oct 17
- Iteration 52.3: Tuesday Oct 18 - Monday Nov 2
- Dashboard: View Priority List
- Release Goal: 5 work items, as work is completed, it will show up in this list
- Current Status - Updated Every Other Week: View Sept 22 Update
37 Total; 0 Open (0%); 13 Resolved (35.14%); 24 Verified (64.86%);
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 20
Firefox 52 Release - Q3-2016/Q4-2016
- Iteration 52.1: Tuesday September 21 - Monday October 3
- Iteration 52.2: Tuesday October 4 - Monday October 17
- Iteration 52.3: Tuesday October 18 - 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 - 52.1
- Duration: Tuesday Sept 20 - Monday October 3
- Iteration Backlog: View in Bugzilla
- Dashboard: View Priority List
- Completion Goal: 4 work items.
10 Total; 1 Open (10%); 2 Resolved (20%); 7 Verified (70%);
Meetings
Planning
| Day of week | Pacific Time | Eastern Time | Central European Time | Indian Time |
|---|---|---|---|---|
| Tuesdays | 9:00AM - 11:00AM | 11:00AM - 1:00PM | 5:00PM - 7:00PM | 9:30PM - 11:30PM |
- Frequency: One meeting per week on Tuesday.
- Duration: 2 hours
- Vidyo Room: FXPrivacy
- IRC: #privacy
Status Update
| Day of week | Pacific Time | Eastern Time | Central European Time | Indian Time |
|---|---|---|---|---|
| Monday, Friday | 8:00AM - 8:30AM | 11:00PM - 11:30AM | 5:00PM - 5:30PM | 8:30PM - 9:00PM |
- Frequency: Two meetings per week on Monday and Friday
- Duration: 30 min
- Vidyo Room: FXPrivacy
- IRC: #privacy
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.
