Closed Bug 1768046 Opened 3 years ago Closed 3 years ago

DevTools Release Tasks - Cycle 102

Categories

(DevTools :: General, task)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

(Blocks 1 open bug)

Details

Soft Freeze / Merge Date: 2022-05-26 / 2022-05-30 (from the Release Management Calendar)
More details about any of those tasks can be found at: https://firefox-source-docs.mozilla.org/devtools/release.html

Anytime during the release:

  • ✅ outdated backward compatibility code removed (doc, searchfox)
  • ✅ outdated telemetry probes removed (bz query)
  • ✅ Remove old perf panel (Bug 1668219)

Close to the end of the release

  • ✅ smoke test for remote debugging against version 101 (doc)
  • ✅ smoke test for remote debugging against the same version (version 102) (same doc)
  • ✅ check xpcshell debugging (doc)

WebDriver BiDi / Marionette:

Template suggestion for the WebDriver email (adjust wording if relevant):

Firefox 101 has just been released, containing updates for our WebDriver (BiDi, Marionette) support.

You can find all the details in the change log for web developers:

https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/101#webdriver_conformance_webdriver_bidi_marionette

See https://docs.google.com/document/d/1t8pR_lcTkjZjX1ddOf6tyvPY8dtE519Vlu8wXX58x_E for detailed explanations about Marionette tasks, or contact :whimboo / :jdescottes for help


Nice to have:

Depends on: 1668219
Depends on: 1769026

For the release notes of Marionette and WebDriver BiDi I've opened the following PR:
https://github.com/mdn/content/pull/16657

Depends on: 1771143

The email to the WebDriver group has been sent out: https://groups.google.com/a/mozilla.org/g/dev-webdriver/c/EUzY7k60Www

It's all done.

Julian, please update the template and the generator for the modified WebDriver bug query and email template.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(jdescottes)
Resolution: --- → FIXED
Flags: needinfo?(jdescottes)
You need to log in before you can comment on or make changes to this bug.