-
Notifications
You must be signed in to change notification settings - Fork 569
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 - 2016-04-25 #95
Comments
It might be good to append to #92 some sort of timing as to when we would want to do another minor release on v4 I'd like to also discuss #86 (Tracking async wrap changes). Also would be good to discuss if this should be a minor or not (something that would align with the above point) Would be good if @trevnorris could join us I know we never agreed on anything, but I would like to potentially continue the discussion about naming which we have in #63. I have seen multiple individuals running on v5 who are surprised to find regressions and new bugs showing up on that stream. This is opening an inevitable bikshed, so I think it would be best to avoid discussing what to name it, but to come to an agreement that renaming is on the table. We have 6 months before I think this is entirely necessary, as anyone on v6 will get grandparented into LTS. This also serves as a good natural timing to make the change. We have three pr's sitting on master to be discussed: @Fishrock123's timer refactor nodejs/node#4007 @misterdjules's domain fix nodejs/node#4659 @saghul's libuv update nodejs/node#5994
|
Having slight technical difficulties on my end with internet connection... |
Link to doc for minutes: https://docs.google.com/document/d/1zJL6n2vhQ3Fm8xgTWIe2w7aSVO0Kt2ITqpfiRwFH-ic/edit |
When
2016-04-25 @ 01:00pm Pacific
Who
@nodejs/lts
Where
Google Hangout On Air (details to be posted later)
Agenda
nodejs/LTS
nodejs/LTS
The text was updated successfully, but these errors were encountered: