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 - 2016-03-21 #89

Closed
jasnell opened this issue Mar 21, 2016 · 8 comments
Closed

LTS Meeting - 2016-03-21 #89

jasnell opened this issue Mar 21, 2016 · 8 comments

Comments

@jasnell
Copy link
Member

jasnell commented Mar 21, 2016

When

2016-03-21, 1-2pm Pacific

Invited

@nodejs/lts

Participation

Minutes

https://docs.google.com/document/d/1BP2YcL4c1YLSe4L3YlOZd12OnSAGgUj2SoaESUHAxuI/edit?usp=sharing

Agenda

nodejs/node

  • buffer: backport --zero-fill-buffers command line option: #5751, #5748, #5744
  • Backporting the new Buffer APIs to v4, v0.12 and v0.10
  • Update npm to 2.x in Node 0.10 #5570

nodejs/LTS

  • Support from V8 for Node's LTS releases #88
  • Track backporting Path optimizations #87
@zkat
Copy link

zkat commented Mar 21, 2016

I'll be around for the first half hour of this -- the npm CLI meeting is at 13:30PDT.

As far as the npm side of this meeting, these are the PRs for:

@MylesBorins
Copy link
Contributor

@jasnell is the meeting at noon PST or 1 PST

all mixed up due to DST

@Fishrock123
Copy link
Contributor

When is this?

@jasnell
Copy link
Member Author

jasnell commented Mar 21, 2016

Ha! Crap... forgot the time. 1pm pacific

@MylesBorins
Copy link
Contributor

Some PR's that have the LTS-agenda flag

debugger: introduce exec method for debugger nodejs/node#1491
Refactor Timers nodejs/node#4007
domain: fix clearing domains stack nodejs/node#4659
Path updates (various PR's to cover all regressions)

@jasnell
Copy link
Member Author

jasnell commented Mar 21, 2016

odd... the node-meeting-agenda tool did not pick up on these additional items (/cc @rvagg)

@MylesBorins
Copy link
Contributor

@jasnell is it only running on the LTS repo? These were all from nodejs/node

@rvagg
Copy link
Member

rvagg commented Mar 22, 2016

hum, we had the same issue in the last CTC meeting with an issue not being picked up in nodejs/TSC, perhaps something has changed with the GH API, will have to investigate!

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

5 participants