Platform/GFX/WebRender2020 Q1: Difference between revisions

From MozillaWiki
< Platform‎ | GFX
Jump to navigation Jump to search
(updates)
(edits)
Line 15: Line 15:
* 72 (Jan 7)
* 72 (Jan 7)
** WR on Android for Pixels 2, 3, 2XL and 3XL
** WR on Android for Pixels 2, 3, 2XL and 3XL
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1600133
** WR for Nvidia laptops with small screen
** WR for Nvidia laptops with small screen
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1566875
* 73 (Feb 11)
* 73 (Feb 11)
** WR on Adreno 5xx and 6xx families https://bugzilla.mozilla.org/show_bug.cgi?id=1602597
** WR on Adreno 5xx and 6xx families  
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1602597
* 74 (March 10)
* 74 (March 10)
** WR on a specific slice of Intel Laptions (TBD based on compositor work)
** WR on a specific slice of Intel Laptions (TBD based on compositor work)

Revision as of 17:45, 10 December 2019

WebRender Q1 2020

The purpose of this document is to highlight our priorities for WebRender in Q1 of 20202

Where have we shipped WebRender?

For a list of the various places we have shipped WebRender, see: https://wiki.mozilla.org/Platform/GFX/WebRender_Where

Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features

Core Priorities

Shipping WebRender

We want to keep shipping WebRender to as many targets as possible each quarter. Below is a list of releases in Q1 and what we are aiming to ship per release:

As part of this effort, we will need to monitor and fix any critical correctness or perf bugs that appear that could potentially block shipping those targets. Here is a list of metabugs where we will track any key bugs we will be monitoring for this effort: