Node.js Foundation Release WorkGroup Meeting 2019-02-14

[mhdawson]

Time

UTC Thu 14-Feb-2019 16:00 (04:00 PM):

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

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Release%20WorkGroup+Meeting+2019-02-14&iso=20190214T16
• or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Feb+14%2C+2019+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1EfloksCjF569wpccSPn8RJSLtsGVhNhwT-_HQSEynyg/edit

Agenda

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

nodejs/node

• Should libuv upgrades be semver-minor? #25785
• [v6.x backport] src: add environment cleanup hooks #22633

nodejs/Release

• doc: update to reflect N-API #410
• Plan for Node.js 11 Current releases #397
• doc: update the releaser onboarding process and rules #393
• Final 6.x release before EOL? [Discussion] #414

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]

Sorry can't make it this week as I'm at IBM's Think conference.

[richardlau]

Unsure if I'll make this week's meeting as I'm currently recovering from a cold. I've added #414 to the agenda -- I think we should keep track of it until we decide one way or the other about doing another 6.x release.

[BridgeAR]

I guess we need a new host since @mhdawson is not able to attend?

I just started another zoom session https://us04web.zoom.us/j/906555115

[targos]

I forgot about the meeting... Coming asap

[BridgeAR]

Only @targos, @richardlau and me were able to join today and since most open questions are about @nodejs/lts we skipped the main agenda. Instead we suggest to have another meeting on Monday 18.02. the same time if that fits the others.

#393 seems uncontroversial and it should likely just land?

#25785 I personally feel we could just document that here: https://github.com/nodejs/node/blob/master/doc/guides/contributing/pull-requests.md#dependencies

[BethGriggs]

Sorry I missed this one, something came up last minute 😞 - Thank you for taking it over @BridgeAR

I agree with #393 being good to land.

[BethGriggs]

I landed "doc: update to reflect N-API #410" as it had 6 approvals. We have also agreed to do a final 6.x release in #414.

The two items to be carried over to the agenda next week will be

• Should libuv upgrades be semver-minor? #25785
• Plan for Node.js 11 Current releases #397