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

[v8] Define version support policy & next major schedule #9831

Closed
Tracked by #9508
mydea opened this issue Dec 14, 2023 · 1 comment
Closed
Tracked by #9508

[v8] Define version support policy & next major schedule #9831

mydea opened this issue Dec 14, 2023 · 1 comment
Milestone

Comments

@mydea
Copy link
Member

mydea commented Dec 14, 2023

When shipping v8, we want to be more transparent about when (approximately) we plan on shipping v9, as well as what versions we plan on dropping support for then.

This does not need to be an exact date, but something that users can orient around.

I would suggest either a 6 or 9 month period (so ~July or October 2024 for v9).

New Version support in v9:

  • Node 16+
  • ES2018

Open questions

  • What timerange do we want to plan for? 6 months, 9 months, ...?
  • Do we plan to keep Node 16 support, or raise this even further?
  • Do we want to raise ES support?

I don't think we need to be super strict here, it's mostly about adding a docs page to the repo that outlines our rough plans so that this is somewhat transparent, and it is also helpful for ourselves to kind of know when this will come around and plan accoridngly.

@mydea mydea added this to the 8.0.0 milestone Dec 14, 2023
@mydea mydea mentioned this issue Dec 14, 2023
@AbhiPrasad
Copy link
Member

Closing this because we've made decisions for generic v8 support. We can think about long term LTS plans after v8 comes out.

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

2 participants