Firefox/Performance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Fix queries)
m (Fix bug list header)
Line 51: Line 51:
<p> </p>
<p> </p>


==Bug Lists==
{| class="wikitable collapsible" style="width: 100%"
{| class="wikitable collapsible" style="width: 100%"
! Triage
! Triage

Revision as of 22:22, 22 January 2018

Firefox Desktop Perceived Performance Team

The purpose of this team is to improve the perceived performance of the Firefox. Our focus is mostly on frontend code that impacts the perceived performance of the browser itself, not that of web pages. Other teams are focused on that piece.

Members

  • Mike Conley (:mconley)
  • Florian Queze (:florian)
  • Paolo Amadini (:paolo)
  • Gijs Kruitbosch (:Gijs)
  • Philipp Sackl (:phlsa)
  • Panos Astithas (:past)

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
  • 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. 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:
  • perf keyword.
  • qe-verify-, unless it is a bug that QA can reasonably verify.

Adding a New Bug to the Backlog

  1. Add the perf keyword.
  2. Set the bug as a dependency of a user story bug or a meta bug if applicable.
  3. 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.
  2. Leave the priority field empty (--).

Bug Lists

Triage

Collection of work waiting for the team to review and determine if it should be included in the Product Backlog - View in Bugzilla

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);

Backlog

The Product Backlog - View in Bugzilla

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);