readme: update LTS plan based on new release plan and openssl lts #36
Conversation
| which it moves into Maintenance only mode until ~~April 1st, 2017~~ | ||
| December 31st, 2016. | ||
| 4. On or around October 1st, 2016, `v6.x.x` transitions into | ||
| the second LTS release. | ||
| 5. LTS for v4.4.1 continues until April 1st, 2017, after which it | ||
| moves to Maintenance mode until around April 1st, 2017. |
jasnell
force-pushed
the
schedule-adjustment
branch
from
1be6bf0
to
043e2ea
Compare
jasnell
force-pushed
the
schedule-adjustment
branch
from
043e2ea
to
6085390
Compare
|
@Fishrock123 ... hopefully all of the dates are correct now. |
| @@ -110,7 +116,7 @@ beyond the LTS release. | |||
| <td>v0.12</td> | |||
| <td>(current)</td> | |||
| <td>2016-04-01</td> | |||
| <td>2017-04-01</td> | |||
There was a problem hiding this comment.
perhaps this should be a strikethrough as well?
| has therefore decided that the best approach is to shorten the | ||
| maintenance period for v0.12 and align it's end date with that of | ||
| OpenSSL v1.0.1's end date. | ||
|
|
There was a problem hiding this comment.
It is better to add an official reference to
https://www.openssl.org/policies/releasestrat.html
as there is a possibility to change their policy and schedule in the future.
|
@jasnell Could you please update this? @yosuke-furukawa wrote a blog in Japanese to explain LTS policy and schedule for introducing Node-v5.0, Argon and the forthcoming NodeFest and I found LTS end of v0.12 here has not been updated yet. |
|
^^^^^ Just noticed this was never merged either. |
|
Yes I'll get this updated but it will likely be tomorrow
|
|
#66 states that it is unclear when 0.12 LTS support will end. |
| <p><img src="https://camo.githubusercontent.com/675f052419c56a583c19644d4da30cc0ff4e02bb/68747470733a2f2f636c6475702e636f6d2f6c4d48746245334e72782d3330303078333030302e706e67" alt="Strawman LTS Schedule"/></p> | ||
|
|
||
| (note: the diagram above shows v0.12 maintenance expiring in April 2017. That | ||
| date has been changed to December 31st, 2016.) |
There was a problem hiding this comment.
Why does this PR update the actual in-tree LTS Schedule with an out-of-tree Draft schedule that has one date invalid?
There was a problem hiding this comment.
Note: this specific change still doesn't look good to me.
|
this just ended up on my radar, is there a reason we have not landed this yet? |
|
What happened to this? Note that the LTS schedule is both linked from 6.0.0 release blog post and incorrect. |
| @@ -9,13 +9,12 @@ The Current LTS Plan is: | |||
| 1. The next LTS release will be cut from the Converged Repo (nodejs/node) once | |||
| the convergence of the joyent/node and nodejs/io.js streams has been | |||
| completed. The current target is to move to the fully converged stream by | |||
| the end of August, 2015, with the first LTS release cut during the first | |||
| week of October, 2015. | |||
| the end of August, 2015, with the `v4.x` stable branch transitioning to LTS around the first week of October, 2015. | |||
|
I will work on getting this updated tomorrow |
|
Is this PR still applicable? |
|
Actually, I think this can be closed now. |
with OpenSSL v1.0.1 LTS end
/cc @nodejs/lts