Skip to content

Latest commit

 

History

History
80 lines (57 loc) · 5.58 KB

README.md

File metadata and controls

80 lines (57 loc) · 5.58 KB
Raw

Releases WG

Oversees all release branches, and tooling to support releases.

Membership

Avatar Name Role Time Zone
@codebytere Shelley Vohr @codebytere Chair CET (Berlin)
@jkleinsc John Kleinschmidt @jkleinsc Member ET (Harrisburg)
@ckerr Charles Kerr @ckerr Member CT (New Orleans)
@vertedinde Keeley Hammond @VerteDinde Member PT (Portland)
@marshallofsound Samuel Attard @MarshallOfSound Member PT (Vancouver)
@mlaurencin Michaela Laurencin @mlaurencin Member ET (Boston)
@clavin Calvin Watford @clavin Member MT (Salt Lake City)
@georgexu99 George Xu @georgexu99 Member PT (Seattle)
@dsanders11 David Sanders @dsanders11 Member PT (Santa Barbara)

Emeritus Members

Emeritus Members
Avatar Name Role Time Zone
@sofianguy Sofia Nguy @sofianguy Member PT (San Francisco)
@deermichel Micha Hanselmann @deermichel Member CET (Prague)
@amclegg Anna Clegg @amclegg Member PT (San Francisco)
@alexeykuzmin Alexey Kuzmin @alexeykuzmin Member CET (Prague)
@binarymuse Michelle Tilley @BinaryMuse Member PT (San Francisco)
@erickzhao Erick Zhao @erickzhao Observer PT (San Francisco)
@deepak1556 Deepak Mohan @deepak1556 Member JST (Nagano)
@zcbenz Cheng Zhao @zcbenz Member JST (Nagoya)
@raisinten Darshan Sen @raisinten Member IST (Kolkata)

Areas of Responsibility

  • 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
  • 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.

Leadership Responsibilities

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.

Associated Repositories

See repos.md

Rules for Membership

In order to join the Releases Working Group, an aspiring member must:

  1. Regularly attend three meetings
  2. Request entry into Releases Working Group by asking the current Chair
  3. Obtain consensus approval by vote of existing membership during a portion of a meeting which the requester shall not attend.

WG Removal Policy

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 Schedule

  • Sync Meeting 1 hour each Wednesday, alternating between two times: 16:30 UTC and 23:00 UTC.

Meeting notes may be viewed in meeting-notes.