Skip to content

Latest commit

 

History

History
50 lines (38 loc) · 1.9 KB

2019-05-01.md

File metadata and controls

50 lines (38 loc) · 1.9 KB

Release WG Minutes

Date: 2019-05-01

Attendees

Members

  • @codebytere
  • @sofianguy
  • @marshallofsound
  • @jkleinsc
  • @robo

Visitors

  • @hashimoto

Agenda

Please add your agenda items here with the name of the person adding the item

  1. (@codebytere) Where should the 5.0.0 retro live?
    • Do we think it should be ephemeral (not put into version control) or potentially added to a new retro section of the Release WG dir inside the gov repo?
    • Verdict: PR into gov repo
  2. (@codebytere) Should Electron invest in its own paid Heroku team?
    • Verdict: Yes, ask the Admin WG
  3. (@sofianguy) Let's talk release dates again
    • #17923
    • Verdict: done, no action needed
  4. (@marshallofsound) Open floor for release process hardening, it should be 1-click and go so how can we make sudowoodo more resilient to failures in third party systems. i) Retry GH api requests in the release notes phase #18085 ii) Make the prepare-release Sudowoodo step retryable

Backport Requests

Nota Bene: If you are the requester, you are generally expected to attend the meeting. If you are unable to do so, please state your reason for requesting the backport.

  • #18016 MarshallOfSound
    • Verdict:
      • Backport to 6-0-x
      • Drop support for 4-1-x and release new 4-2-x
  • #17686 MarshallOfSound
    • Verdict: @robo will review and merge

Action Items

  • @codebytere to PR retro into wg-releases subdir in the gov repo
  • @MarshallOfSound to ask the Admin WG about allocation of funds for Heroku paid team
  • @MarshallOfSound to release 4-2-x and backport to everywhere

Follow-Up Discussion

None.