Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Release WorkGroup Meeting 2020-02-27 #539

Closed
mhdawson opened this issue Feb 24, 2020 · 2 comments
Closed

Node.js Release WorkGroup Meeting 2020-02-27 #539

mhdawson opened this issue Feb 24, 2020 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 24, 2020

Time

UTC Thu 27-Feb-2020 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 27-Feb-2020 08:00 (08:00 AM)
US / Mountain Thu 27-Feb-2020 09:00 (09:00 AM)
US / Central Thu 27-Feb-2020 10:00 (10:00 AM)
US / Eastern Thu 27-Feb-2020 11:00 (11:00 AM)
London Thu 27-Feb-2020 16:00 (04:00 PM)
Amsterdam Thu 27-Feb-2020 17:00 (05:00 PM)
Moscow Thu 27-Feb-2020 19:00 (07:00 PM)
Chennai Thu 27-Feb-2020 21:30 (09:30 PM)
Hangzhou Fri 28-Feb-2020 00:00 (12:00 AM)
Tokyo Fri 28-Feb-2020 01:00 (01:00 AM)
Sydney Fri 28-Feb-2020 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from Release-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/Release

Invited

  • Release team: @nodejs/release
  • LTS team: @nodejs/lts

Observers/Guests

Notes

The agenda comes from issues labelled with Release-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Join URL: https://zoom.us/j/157618869

Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure
@mhdawson mhdawson self-assigned this Feb 24, 2020
@richardlau
Copy link
Member

I’m not going to be able to attend this week. For #536 I did post some thoughts around the ESM changes and asked whether all ESM changes should be manually backported (i.e. no cherry picks) due to the difference in flags required.

@BethGriggs
Copy link
Member

ping @nodejs/release please indicate your availability to attend the meeting today

BethGriggs added a commit to BethGriggs/Release that referenced this issue Mar 2, 2020
BethGriggs added a commit to BethGriggs/Release that referenced this issue Mar 2, 2020
BethGriggs added a commit to BethGriggs/Release that referenced this issue Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants