Responsibilities of the Quantum Profiling Pool: Difference between revisions

no edit summary
(Created page with "We would like to make the Quantum Profiling Pool a standard process. Dave Camp and engineering leadership believe increasing our capacity for profiling is essential to realizi...")
 
No edit summary
 
Line 1: Line 1:
We would like to make the Quantum Profiling Pool a standard process. Dave Camp and engineering leadership believe increasing our capacity for profiling is essential to realizing our 2018 performance goals. This is where your help comes in. I would like one representative (at minimum) from each key component, as listed in the Sheet,  to be on the Quantum Profiling Pool. The responsibilities of this group are as follows.
We would like to make the Quantum Profiling Pool a standard process. Dave Camp and engineering leadership believe increasing our capacity for profiling is essential to realizing our 2018 performance goals. This is where your help comes in. I would like one representative (at minimum) from each key component, as listed in the Sheet,  to be on the Quantum Profiling Pool. The responsibilities of this group are as follows.


*
* They will serve for one Quantum Flow iteration (three firefox releases). The next iteration ends Mar 11, 2018 when FF60 leaves Nightly for Beta (https://wiki.mozilla.org/RapidRelease/Calendar ).
* They will serve for one Quantum Flow iteration (three firefox releases). The next iteration ends Mar 12, 2018 when FF60 leaves Nightly for Beta (https://wiki.mozilla.org/RapidRelease/Calendar ).
* They should be able to commit to at least half-a-day a week to profiling.  
* They should be able to commit to at least half-a-day a week to profiling.  
* Their work will come out of Quantum Release Criteria, Quantum Flow and other performance bugs that are marked with whiteboard: [qf:needs-analysis]. These will be assigned round-robin if a component is unknown.
* Their work will come out of Quantum Release Criteria, Quantum Flow and other performance bugs that are marked with whiteboard: [qf:needs-analysis]. These will be assigned round-robin if a component is unknown.
canmove, Confirmed users
1,104

edits