Oversees all release branches, and tooling to support releases.
| Avatar | Name | Role | Time Zone |
|---|---|---|---|
 |
Shelley Vohr @codebytere | Chair | CET (Berlin) |
 |
John Kleinschmidt @jkleinsc | Member | ET (Harrisburg) |
 |
Charles Kerr @ckerr | Member | CT (New Orleans) |
 |
Keeley Hammond @VerteDinde | Member | PT (Portland) |
 |
Samuel Attard @MarshallOfSound | Member | PT (Vancouver) |
 |
Michaela Laurencin @mlaurencin | Member | ET (Boston) |
 |
Calvin Watford @clavin | Member | MT (Salt Lake City) |
 |
George Xu @georgexu99 | Member | PT (Seattle) |
 |
David Sanders @dsanders11 | Member | PT (Santa Barbara) |
Emeritus Members
| Avatar | Name | Role | Time Zone |
|---|---|---|---|
 |
Sofia Nguy @sofianguy | Member | PT (San Francisco) |
 |
Micha Hanselmann @deermichel | Member | CET (Prague) |
 |
Anna Clegg @amclegg | Member | PT (San Francisco) |
 |
Alexey Kuzmin @alexeykuzmin | Member | CET (Prague) |
 |
Michelle Tilley @BinaryMuse | Member | PT (San Francisco) |
 |
Erick Zhao @erickzhao | Observer | PT (San Francisco) |
 |
Deepak Mohan @deepak1556 | Member | JST (Nagano) |
 |
Cheng Zhao @zcbenz | Member | JST (Nagoya) |
 |
Darshan Sen @raisinten | Member | IST (Kolkata) |
- Releasing Electron according to schedule
- Release timeline coordination
- When to cut new branches for major release lines (e.g.
11-x-y) - Planning beta cycles, timelines, etc.
- Listening and responding to feedback
- When to cut new branches for major release lines (e.g.
- Management of Heroku apps for associated repositories
- Triaging issues and organizing beta stabilization issues for discussion.
- Determining which features are allowed to be backported to release lines.
In addition to responsibilities outlined in the Charter, a Chair of the Releases Working Group should:
- Run regular release audits for supported branches using
unreleased.- Check for unmerged backports and pull requests needing manual (non-trop) backports to release branches.
- Ensure releases are run for supported branches passing the pre-set unreleased commit threshold.
- Ensure relevant PRs are being backported to necessary branches, and that original PR openers are opening manual backports for those that trop is unable to handle itself.
See repos.md
In order to join the Releases Working Group, an aspiring member must:
- Regularly attend three meetings
- Request entry into Releases Working Group by asking the current Chair
- Obtain consensus approval by vote of existing membership during a portion of a meeting which the requester shall not attend.
If a sitting member of the WG has not been active in a meaningful way for at least one month, the WG may vote to remove them from its set of sitting members.
This is done primarily to ensure that there are no open avenues of compromise for the project given that the Releases WG confers notable permissions.
Meeting notes may be viewed in meeting-notes.