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 Foundation Build WorkGroup Meeting 2019-04-02 #1744

Closed
mhdawson opened this issue Mar 27, 2019 · 5 comments
Closed

Node.js Foundation Build WorkGroup Meeting 2019-04-02 #1744

mhdawson opened this issue Mar 27, 2019 · 5 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 27, 2019

Time

UTC Tue 02-Apr-2019 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Tue 02-Apr-2019 13:00 (01:00 PM)
US / Mountain Tue 02-Apr-2019 14:00 (02:00 PM)
US / Central Tue 02-Apr-2019 15:00 (03:00 PM)
US / Eastern Tue 02-Apr-2019 16:00 (04:00 PM)
London Tue 02-Apr-2019 21:00 (09:00 PM)
Amsterdam Tue 02-Apr-2019 22:00 (10:00 PM)
Moscow Tue 02-Apr-2019 23:00 (11:00 PM)
Chennai Wed 03-Apr-2019 01:30 (01:30 AM)
Hangzhou Wed 03-Apr-2019 04:00 (04:00 AM)
Tokyo Wed 03-Apr-2019 05:00 (05:00 AM)
Sydney Wed 03-Apr-2019 07:00 (07:00 AM)

Or in your local time:

Links

Agenda

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

nodejs/build

  • Can 'make lint-py PYTHON=python3' be a manditory Jenkins test? #1631
  • Request for elevated permissions #1337
  • Use Foundation resources to support build #1154

Invited

  • Build team: @nodejs/build

Observers/Guests

Notes

The agenda comes from issues labelled with build-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

@mhdawson mhdawson self-assigned this Mar 27, 2019
@Trott
Copy link
Member

Trott commented Mar 27, 2019

Might be good to put nodejs/node#26401 (comment) on the agenda? Maybe we need a standard documented procedure for what to do when core files are requested? (Maybe we have one already? My MO is to rely on refack or someone else to figure out how to do it.)

@refack
Copy link
Contributor

refack commented Mar 27, 2019

Maybe we need a standard documented procedure for what to do when core files are requested?

The trouble is it's very OS dependent (even between Ubuntu majors...).
Regarding node-report: we could add a bunch of --report* args to the stress job.

@refack
Copy link
Contributor

refack commented Mar 27, 2019

#1745 addresses #1631 so I'm taking off the agenda

@rvagg
Copy link
Member

rvagg commented Apr 2, 2019

Awkward time for me, will probably be present but distracted.

@Trott
Copy link
Member

Trott commented Apr 24, 2019

Minutes were added in a3a6d29

@Trott Trott closed this as completed Apr 24, 2019
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

4 participants