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

1. 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.
2. 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

1. Add the [fxperf] tag to the whiteboard.
2. Add the perf keyword.
3. Set the bug as a dependency of a user story bug or a meta bug if applicable.
4. 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

1. Mark the bug as blocking the photon-performance-triage meta bug or add the [fxperf] tag to the whiteboard.
2. Leave the priority field empty (--).

Triage
Collection of work waiting for the team to review and determine if it should be included in the Product Backlog Bugs blocking photon-performance-triage - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Tracked bugs without a priority set - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Releases

Current Release
P1: Must Have - development occurring in the current release - View in Bugzilla Duration: Tuesday January 23 - Monday March 12 Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Current Release: Completed
View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Next Release
P2: Should Have - targeted for the current release if production capacity exists - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Backlog
P3: Could Have - planned for development in an upcoming release - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

Patches Accepted
P5: Will Have - not scheduled for any particular release, patches accepted - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1

¯\_(ツ)_/¯
P4: (should be reprioritized to P3 or P5) - View in Bugzilla Bugzilla query error Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1