-
Notifications
You must be signed in to change notification settings - Fork 577
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
Comments
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
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 |
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. @jasnell can you explain how these shifts impact the 10.0.0 release? |
We have been using the first Tuesday of each month for releases, so I liked
the symmetry for EOL and maintenance bit flip
Open to making it the end of the month though
…On Oct 30, 2017 6:34 PM, "Rod Vagg" ***@***.***> wrote:
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 <https://github.com/jasnell> can you explain how these shifts
impact the 10.0.0 release?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#264 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV8gC8SFwYB4y7McK2o3TN-rGyyj0ks5sxk8EgaJpZM4QH4a1>
.
|
Any more thoughts on this regarding the transition? |
I think end of month makes sense. |
My preference is the end of the month as well. |
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? |
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. |
I've updated the schedule.json and the README.md Closes: nodejs#264
I've updated the schedule.json and the README.md Closes: #264
I've updated the schedule.json and the README.md Closes: nodejs#264
This would be both for 6.x to move to Maintenance and 4.x to go EOL
/cc @nodejs/lts @nodejs/tsc
The text was updated successfully, but these errors were encountered: