Firefox/Performance
Firefox Desktop Perceived Performance Team
The purpose of this team is to improve the perceived performance of Firefox. Our focus is mostly on front-end code that impacts the perceived performance of the browser itself, not the performance of rendering web pages. There are other teams focused on the latter.
Members
- Mike Conley (:mconley)
- Florian Queze (:florian)
- Paolo Amadini (:paolo)
- Gijs Kruitbosch (:Gijs)
- Philipp Sackl (:phlsa)
- Panos Astithas (:past)
Operating principals
Text goes here
Contact
Team Meeting
| Day of week | Pacific Time | Eastern Time | UTC | Central European Time |
|---|---|---|---|---|
| Fridays | 8:30AM - 9:00AM | 11:30AM - 12:00PM | 4:30PM - 5:00PM | 5:30PM - 6:00PM |
- Frequency: One meeting per week on Friday.
- Duration: 30 min
- Vidyo Room: Firefox
- Meeting notes: Google Doc
- IRC: #fx-team
- Mailing list: firefox-dev
Bugzilla
Bugzilla components don't tend to align properly with this project's boundaries, so this team is monitoring bugs across a number of components that block the photon-performance meta bug. Here is the dependency tree. Common components of interest are Firefox:General, Firefox:Tabbed Browser, Toolkit:General and more.
Selecting a New Bug for the Current Release
- 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:
- [fxperf] whiteboard tag.
- perf keyword.
- qe-verify-, unless it is a bug that QA can reasonably verify.
Adding a New Bug to the Backlog
- Add the [fxperf] tag to the whiteboard.
- Add the perf keyword.
- Set the bug as a dependency of a user story bug or a meta bug if applicable.
- Set the bug priority per the following guidelines or call it out for a priority decision in the Weekly Meeting:
- 'P1': Must Have - development occurring in the current release.
- 'P2': Should Have - targeted for next release.
- 'P3': Could Have - planned for development in an upcoming release.
- 'P5': Will Have - not scheduled for any particular release, patches accepted.
Submitting a Bug for Triage
- Mark the bug as blocking the photon-performance-triage meta bug or add the [fxperf] tag to the whiteboard.
- Leave the priority field empty (--).
Releases
| Current Release |
|---|
|
P1: Must Have - development occurring in the current release - View in Bugzilla Duration: Tuesday January 23 - Monday March 12
No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
| Current Release: Completed | |||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6 Total; 0 Open (0%); 6 Resolved (100%); 0 Verified (0%); |
| Next Release |
|---|
|
P2: Should Have - targeted for the current release if production capacity exists - View in Bugzilla No results. 0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%); |
| Backlog | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
P3: Could Have - planned for development in an upcoming release - View in Bugzilla
5 Total; 5 Open (100%); 0 Resolved (0%); 0 Verified (0%); |
| Patches Accepted | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
P5: Will Have - not scheduled for any particular release, patches accepted - View in Bugzilla
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%); |
| ¯\_(ツ)_/¯ | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
P4: (should be reprioritized to P3 or P5) - View in Bugzilla
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%); |