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 Meeting May 15th - 5 pm EST #213

Closed
gibfahn opened this issue May 10, 2017 · 6 comments
Closed

LTS Meeting May 15th - 5 pm EST #213

gibfahn opened this issue May 10, 2017 · 6 comments
Assignees

Comments

@gibfahn
Copy link
Member

gibfahn commented May 10, 2017

Present

@nodejs/lts

When

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

Previous meetings: #201 #194 #185

Where

Hangouts on Air:

Agenda

nodejs/LTS

  • meta: updated messaging regarding dates #141
  • Clarify what happens with odd-numbered releases in April #128
  • meta: charter the LTS Working Group nodejs/CTC#122
  • Potential Semver Minor Backports #177

other

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

Minutes

@gibfahn gibfahn self-assigned this May 10, 2017
@sam-github
Copy link
Contributor

sam-github commented May 11, 2017

@gibfahn The subject says May 15th, the body text says April 15th, and the timeanddate.com link points to May 10th :-)

@gibfahn
Copy link
Member Author

gibfahn commented May 11, 2017

@sam-github Should be fixed.

@mhdawson
Copy link
Member

I'll be there

@MylesBorins
Copy link
Contributor

Where's da link?

@mhdawson
Copy link
Member

Added hangout links

@sam-github
Copy link
Contributor

@nodejs/lts Meeting! Who's coming?

gibfahn added a commit to gibfahn/Release that referenced this issue May 16, 2017
gibfahn added a commit to gibfahn/Release that referenced this issue May 16, 2017
gibfahn added a commit to gibfahn/Release that referenced this issue May 16, 2017
gibfahn added a commit to gibfahn/Release that referenced this issue May 18, 2017
i.e. that there isn't one.

This was agreed in the LTS meeting:
nodejs#213
gibfahn added a commit to gibfahn/Release that referenced this issue May 18, 2017
i.e. that there isn't one.

This was agreed in the LTS meeting: nodejs#213
gibfahn added a commit that referenced this issue May 23, 2017
gibfahn added a commit that referenced this issue May 28, 2017
i.e. that there isn't one.

This was agreed in the LTS meeting: #213

PR-URL: #220
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
ChALkeR pushed a commit to ChALkeR/LTS that referenced this issue Jun 30, 2018
ChALkeR pushed a commit to ChALkeR/LTS that referenced this issue Jun 30, 2018
i.e. that there isn't one.

This was agreed in the LTS meeting: nodejs#213

PR-URL: nodejs#220
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
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