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

Proposing April 4th as LTS transition Date #264

Closed
MylesBorins opened this issue Oct 26, 2017 · 8 comments
Closed

Proposing April 4th as LTS transition Date #264

MylesBorins opened this issue Oct 26, 2017 · 8 comments

Comments

@MylesBorins
Copy link
Contributor

This would be both for 6.x to move to Maintenance and 4.x to go EOL

/cc @nodejs/lts @nodejs/tsc

MylesBorins added a commit to MylesBorins/LTS that referenced this issue Oct 26, 2017
I've updated the schedule.json and the README.md

Not sure the best way to update schedule.ical, how do we create it?

There is a part of me that thinks we should remove it and put the dates
on the official calendar. I'll open another PR for that

Closes: nodejs#264
@jasnell
Copy link
Member

jasnell commented Oct 26, 2017

I'm good on this. I'll be starting the plan for the Node.js 10.0.0 release shortly after cutting 9.0.0, I would anticipate 10.0.0 coming out later in the month so having these transition earlier would be good

@rvagg
Copy link
Member

rvagg commented Oct 30, 2017

Could we just formalise EOL as the end of the month in each case rather than an arbitrary date? We've communicate that we drop support "in April" but doing it this early is likely going to be a very big surprise.
Same case could be made for 6.x moving to Maintenance although that matters much less than dropping 4.x support.

@jasnell can you explain how these shifts impact the 10.0.0 release?

@MylesBorins
Copy link
Contributor Author

MylesBorins commented Oct 30, 2017 via email

@MylesBorins
Copy link
Contributor Author

Any more thoughts on this regarding the transition?

@gibfahn
Copy link
Member

gibfahn commented Nov 15, 2017

I think end of month makes sense.

@mhdawson
Copy link
Member

My preference is the end of the month as well.

@MylesBorins
Copy link
Contributor Author

As we have a release scheduled for April 4th does it make sense to simply "transition" the release line without doing it in a release?

@mhdawson
Copy link
Member

I don't think we actually change anything when we "transition" so unless there is a case were something needs to go in between the 4th and the end of the month simply "transitioning" without a release makes sense to me.

MylesBorins added a commit to MylesBorins/LTS that referenced this issue Nov 17, 2017
I've updated the schedule.json and the README.md

Closes: nodejs#264
gibfahn pushed a commit that referenced this issue Jan 5, 2018
I've updated the schedule.json and the README.md

Closes: #264
ChALkeR pushed a commit to ChALkeR/LTS that referenced this issue Jun 30, 2018
I've updated the schedule.json and the README.md

Closes: nodejs#264
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

5 participants