Platform/GFX/Quantum Render: Difference between revisions

Jump to navigation Jump to search
→‎Vital stats: Updated metabugs and priority definitions
(→‎Vital stats: Updated metabugs and priority definitions)
Line 7: Line 7:
Canonical code repository: https://hg.mozilla.org/mozilla-central <br/>
Canonical code repository: https://hg.mozilla.org/mozilla-central <br/>
Bugzilla Component: [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A%20WebRender Core :: Graphics: WebRender] <br/>
Bugzilla Component: [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A%20WebRender Core :: Graphics: WebRender] <br/>
Tracking metabug: {{bug|1311790}} <br/>
Tracking metabugs: <br/>
<ul>
<li>Blocking Nightly : {{bug|1386665}}</li> 
<li>Blocking Beta: P1s on {{bug|11386669}} </li>
<li>Blocking Release: P2s on {{bug|11386669}}
</ul>
General prioritization metric for our stage-wr-trains bug ({{bug|11386669}}) is:
<ul>
<li>P1: block "riding into beta"
very important - looking to find owners and land fixes asap
could be blocking other WR development or solid use of the feature
can't get into beta with these unresolved.</li>
<li>P2: block "riding into release"
not blocking other developers or solid use of the feature, but it shows a regression or correctness problem that we can't ship with. 
We can ride into beta with these, but they need to be fixed before we ride-to-release </li>
<li>P3: needs a call to determine if they should block MVP (bugs here will graduate to P2 or move to Next)
Bugs
</ul>
Mailing list: [https://lists.mozilla.org/listinfo/dev-tech-gfx dev-tech-gfx@lists.mozilla.org] <br/>
Mailing list: [https://lists.mozilla.org/listinfo/dev-tech-gfx dev-tech-gfx@lists.mozilla.org] <br/>
IRC channel: #gfx <br/>
IRC channel: #gfx <br/>
Confirmed users
654

edits

Navigation menu