Releases WG

Date: 2020-05-20

Members

@codebytere
@sofianguy
@MarshallOfSound
@ckerr
@deepak1556
@zcbenz
@jkleinsc
@VerteDinde

Visitors

Agenda

What should/should not get merged during the quiet week? (@jkleinsc)
- What is the goal of the quiet week?
- We should prioritize stability
- Discussion continued in retro ⬇️
9.0.0 retro (@sofianguy ~45 mins)
- https://github.com/electron/governance/projects/6
- outcome action items:
  1. Add a stable prep check list item to kick off final release of the last supported major version before it becomes EOL. Also add a deprecation/EOL notice in the release notes of that release.
  2. (@codebytere) Make and require labels for all PRs, specificially to identify breaking changes PRs.
    - e.g., semver/minor label
  3. Keep blog post and release notes as separate resources
  4. Make sure release notes are ready when we kick off stable release. Blog post will still be published on the release date/when chromium releases
  5. Eliminate quiet week but keep target dates as goals to ensure we don't lose sight of landing changes on time
  6. Add tests to release notes generator
  7. Test build process changes

Backport Requests

Pending votes

Action Items

Follow-Up Discussion

Backport request label change
- Has this been done:q in e/e?
- What (if any) bot changes are needed?