Platform/GFX/Quantum Render: Difference between revisions

Jump to navigation Jump to search

Platform/GFX/Quantum Render (view source)

Revision as of 18:37, 12 April 2019

1,887 bytes removed ,  12 April 2019
copy edits
(added link to roadmap)
(copy edits)
Line 3: Line 3:
The goal of the Quantum Render project is to take the WebRender compositor in Servo and embed it in Firefox. It will replace Gecko's existing compositor, interfacing with Gecko's main-thread layout code. As WebRender is written in Rust and uses a very different design approach, we expect to get stability and performance benefits from this switch.
The goal of the Quantum Render project is to take the WebRender compositor in Servo and embed it in Firefox. It will replace Gecko's existing compositor, interfacing with Gecko's main-thread layout code. As WebRender is written in Rust and uses a very different design approach, we expect to get stability and performance benefits from this switch.


== Roadmap ==
== Planning ==


High-level roadmap for WebRender in 2019:
WebRender roadmap and more detailed quarterly plans:
 
(You'll also find links to various tracking metabugs here)
https://github.com/orgs/FirefoxGraphics/projects/1


== Vital stats ==
== Vital stats ==
Line 13: Line 12:
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 metabugs: <br/>
<ul>
<li>Blocking Nightly : {{bug|1386665}}: https://mzl.la/2wlbV2s </li> 
<li>Blocking Beta: P1s on {{bug|1386669}} https://mzl.la/2LA1Ljm </li>
<li>Blocking Release - looking for owners now: P2s on {{bug|1386669}} https://mzl.la/2CnYS5F </li>
<li>Blocking Release - will get moved to P2 when existing P2s are fixed : P3s on {{bug|1386669}} https://mzl.la/2wLNsmn </li>
<li>Untriaged https://mzl.la/2CsuGmL</li>
<li>Need a priority call if they block: P4s on {{bug|1386669}}: https://mzl.la/2QWWLsO </li>
<li>P2 67: https://mzl.la/2Tl4Awv</li>
<li>P3 67: https://mzl.la/2tBvUIf</li>
<li>P1 68: https://mzl.la/2CKouay</li>
<li>P2 68: https://mzl.la/2CIkojq</li>
<li>P3 68: https://mzl.la/2Yz2aKt</li>
<li>Android MVP: https://mzl.la/2IDSnz0</li>
</ul>
General prioritization metric for our stage-wr-trains bug ({{bug|1386669}}) is:
<ul>
<li>P1: block "riding into beta"
<ul>
<li>very important - looking to find owners and land fixes asap
<li>could be blocking other WR development or solid use of the feature
<li>can't get into beta with these unresolved.
</ul>
</li>
<li>P2 & P3: block "riding into release"
<ul>
<li>not blocking other developers or solid use of the feature, but it shows a regression or correctness problem that we can't ship with. 
<li>We can ride into beta with these, but they need to be fixed before we ride-to-release
<li>P2s should be the list developers look at to find their next WR bug
<li>If there are no currently unassigned P2 bugs, ping mreavy in #gfx on irc
</ul>
</li>
<li>P4: needs a call to determine if they should block MVP (we are typically waiting on info to make a decision)
</ul>
Meta bugs for follow-on work:
<ul>
<li>Blocking Next (bugs blocking next release after MVP): {{Bug|1386674}}</li>
<li>Blocking Android bugs: {{Bug|1485449}}</li>
<li>Blocking Mac bugs: {{Bug|1479789}}


<li>Blocking Linux: {{Bug|1491303}}
Triage info: [[https://wiki.mozilla.org/Platform/GFX/TriageSchedule]]
</ul>
Triage info: https://gist.github.com/Gankro/b05d5bb8c91faff6d23e1d2549e26fe4


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/>
Jbonisteel
428

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1210539"

Navigation menu