[meta] Lighthouse 6.0 Burndown

Channeling our ancestors, we introduce the new abbreviated major release burndown list.

6.0 final scope

• (see all: https://github.com/GoogleChrome/lighthouse/labels/6.0)
• T&S added as a group to BP [@Beytoven] (PR #10623)
• add “mixed content” wording into “https” (PR #10712) [@Beytoven]
• new metrics actionability
• • LCP #10517
• • CLS #10702
• • long tasks #10736
• window.location for finalUrl [@paulirish, @patrickhulce] (PR #10339)
• add desktop scoring curves to LCP/TBT [@brendankenny] (PR #10756)
• roll 1.0.0 of adspeed plugin [@paulirish]

Punting to 6.1

• fold experimental config into default? [@connorjclark]

6.0-beta.0 scope

(need to triage a bit )

New audits

• Total Blocking Time
  • land it (PRs #8975, #9409)
  • Update score curve from HTTPArchive distributions [@brendankenny]
  • web.dev docs (https://github.com/GoogleChrome/web.dev/issues/1627)
• Largest Contentful Paint
  • Land observed impl (PR #9706)
  • Land lantern impl/audit [@connorjclark]
  • web.dev docs (https://github.com/GoogleChrome/web.dev/pull/1639)
• New axe audits #7127
  • land new audits (PR #9798) [@brendankenny]
  • web.dev docs (https://github.com/GoogleChrome/web.dev/issues/1629)
• Cumulative Layout Shift
  • land it (PR #9037) [@paulirish]
  • make decisions about it 😃

Lantern

• “Fixed RTT” calculation [@paulirish]
• Keep first paint events (#9627) [@connorjclark]
• Remove min task duration #9910 [@warrengm]
• data URI server response time (#9833) [@patrickhulce]

Scoring

• check latest HTTPArchive distributions for major drift from current metric score curves [@brendankenny]
• apply new LH 6.0 score weightings [@paulirish]
  • deprecate any existing metrics [@paulirish]
• desktop curves #9436 [@connorjclark ]
• revise scoring documentation (https://github.com/GoogleChrome/web.dev/issues/1630) [@kaycebasques]
  • take another pass on this and merge in work from here and probably here [@paulirish]
  • these docs need to be updated https://github.com/GoogleChrome/lighthouse/blob/d2ec9ffbb21de9ad1a0f86ed24575eda32c796f0/docs/scoring.md#how-are-the-scores-weighted
• ~Move PWA fastenough check to use TBT instead?~ Punting for now and keeping it dependent on TTI. Moving to TBT doesn’t appear to be a clear win.

New gatherers

• main-document-content #9756 (PR #9781) [@brendankenny]

Core misc

• iframe page dependency fix (PR #9727) [@patrickhulce]
• ~redirect/first vs last navstart cleanups #8984 [@brendankenny]~ #10339 handled the part we wanted for 6.0
• nexus 5x -> moto g4 labeling change [@connorjclark]
• ~i18n plugin things~

Lighthouse CI [@patrickhulce]

• MVP burndown list: https://github.com/GoogleChrome/lighthouse-ci/issues/9

Extension

• retire the full-LH extension (PR #9193) [@connorjclark]

DevTools [@connorjclark]

• Add device emulation flag #9377
• New design / Throttling removal / logo
• OOPIFs in DevTools Audits panel are not analyzed
• Write throttling Learn More doc [cjamcl, paulirish]

PSI

• New field data thresholds [@paulirish]
• reanalyze prompt. redirect & amp [@exterkamp]
• Make comms for v6.0.0 PSI scoring changes [@egsweeny]

Plugins

• QoL improvements #9052 [@paulirish]
• Write Plugins learn more doc [@egsweeny]
• “Community plugins beta” in DevTools [@connorjclark]
  • build step [@brendankenny]

Budgets

• Add timing budgets #8917 [@khempenius]

Stack Packs

• Pick and merge new packs from lighthouse-stack-packs (PR #9797) [@exterkamp]
• i18n strings [@exterkamp]

Puntable

Core breaking changes (#9180)

• Remove path support for --extra-headers (and possibly budget-path?) as now users can use cli-flags-path
• (possibly) remove maxWaitForFcp timeout and look directly for the early load-failure cases (DNS, bad cert, etc) - https://github.com/GoogleChrome/lighthouse/pull/9509#issuecomment-518408375
• ~outstanding i18n tasks? #7238 [@exterkamp]~ none for 6.0
• ~(possibly) refactor i18n section in proto to use Map<string, string> instead of RendererFormattedStrings~

Report

• mobile or desktop run indicator at the top of the report #9379

[connorjclark]

6.0 is LIVE.

[natusvince]

@paulirish / @addyosmani - Is there a timeline for LightHouse 6.0 to be released?

+1