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

LTS WG Meeting 17 July 2017 #235

Closed
mhdawson opened this issue Jul 17, 2017 · 6 comments
Closed

LTS WG Meeting 17 July 2017 #235

mhdawson opened this issue Jul 17, 2017 · 6 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Jul 17, 2017

I see by the schedule the meeting is set for today. @gibfahn has been raising the issues lately but he is on vacation for a few weeks so I'm opening this one now (better late than never).

Present

@nodejs/lts, maybe @nodejs/release if they're interested

When

9PM Monday July 17th UTC, or in your local timezone:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+LTS+Working+Group+Meeting&iso=20170626T17&p1=179&ah=1

Previous meetings: #233

Where

Hangouts on Air:

Agenda

nodejs/node

  • CI: test with --with-snapshot on the slower platforms #14222
  • tracking issue: full VS2017 support #13052
  • (v6.x backport) src: allow CLI args in env with NODE_OPTIONS #12677
  • inspector: enable --inspect-brk in v6 #12615
  • Remove indexOf usage from tests in favor of includes #12586

nodejs/LTS

  • doc: charter the Release working group #223

nodejs/CTC

  • Chartering the Release Team as a Working Group #123
  • meta: charter the LTS Working Group #122

Any questions in #node-dev on IRC or comments in this thread

Please 👍 if you can make the meeting, and 👎 if you cannot.

@MylesBorins
Copy link
Contributor

MylesBorins commented Jul 17, 2017 via email

@sam-github
Copy link
Contributor

I can make the time, but skipping seems reasonable, if we all comment on those issues in github.

@mhdawson
Copy link
Member Author

mhdawson commented Jul 17, 2017

I'd really like to get to closure on #223 if we are agreed that we are ready to go (assigned for CTC review/approval) modulo last remaining nits, I think we can cancel, otherwise I think we should have a conversation in the meeting to get agreement on what else needs to change.

@sam-github
Copy link
Contributor

I don't have any comment on #223, it LGTM. Though I don't understand why every WG needs to rediscuss the boilerplate (CONTRIBUTING.md, etc), it seems like they should be the same for all WGs. If all the comments have been addressed, can't it just be landed?

@MylesBorins
Copy link
Contributor

I've just put my notes on #223
Overall looks v good, just a handful of nits. I don't think having the meeting is going to help flesh it out any further than it currently is... but more than happy to attend

@mhdawson
Copy link
Member Author

@MylesBorins thanks, I'll push an update to address the new comments and then I'd like to add to the agenda for the CI.

I'll cancel the meeting for today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants