-
Notifications
You must be signed in to change notification settings - Fork 570
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
npm LTS #14
Comments
@zkat ... would you be able to join us for the next LTS WG meeting to discuss npm LTS? |
Hey! Sorry for the delay. I had trouble pinning down the info I needed to be able to give you a good response about this. But now I have it! So! I can do next Monday at 13:00 PT if that's alright, assuming that's still the time for it? :) /cc @othiym23 |
I will do my best to get @zkat up to speed with my (wooly, vague) thoughts about how npm can best support the LTS process before the meeting. |
Closing this in favor of #37 |
Following up from @zkat's comment in the summit repo about npm 2.x LTS: openjs-foundation/summit#1 (comment) we should pull that discussion into here because we're going to have to care about this for 0.12 maintenance at least. We should ensure that we have synchronized goals and ideas about what LTS means so that we don't end up in conflict about what we're happy to pull in for npm for LTS releases.
@zkat perhaps you could tune us in to ongoing discussions about npm LTS or maybe someone over there could join our meeting next week to sync? Monday 1pm PT.
The text was updated successfully, but these errors were encountered: