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

Mirror node LTS in terms of supported nodes #650

Closed
stefanpenner opened this issue Oct 11, 2016 · 5 comments
Closed

Mirror node LTS in terms of supported nodes #650

stefanpenner opened this issue Oct 11, 2016 · 5 comments

Comments

@stefanpenner
Copy link
Contributor

Without this, other tools that take this approach cannot utilize or depend on this. This would be unfortunate, since we already transpile here and most of our code is reasonably portable.

@stefanpenner
Copy link
Contributor Author

stefanpenner commented Oct 11, 2016

Also note: I am not just "feature requesting" this, rather actually interested in committing to this effort, and also helping maintain this going forward. I am hoping being a strong advocate will help sway choices here.

Please don't hesitate to reach out if ya'll want to discuss this further.

@nathanhammond
Copy link

We should probably open this against the RFCs repo.

@nathanhammond
Copy link

RFC up. This issue should probably be closed in favor of the RFC.

Worth noting that @stefanpenner, myself, and the rest of the Ember ecosystem stand behind this proposal and will contribute maintenance time.

@sebmck
Copy link
Contributor

sebmck commented Oct 12, 2016

Going to move discussion for this over to the RFC @nathanhammond opened. We should definently track LTS releases, we currently test CI on Node 4 and 6.

@sebmck sebmck closed this as completed Oct 12, 2016
@stefanpenner
Copy link
Contributor Author

yarnpkg/rfcs#1

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

No branches or pull requests

3 participants