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

readme: update LTS plan based on new release plan and openssl lts #36

Closed
wants to merge 1 commit into from

Conversation

@jasnell
Copy link
Member

jasnell commented Aug 18, 2015

  • Update the details based on the adopted release plan
  • Modify the v0.12 maintenance expiration date to align
    with OpenSSL v1.0.1 LTS end

/cc @nodejs/lts

README.md Outdated
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.

This comment has been minimized.

Copy link
@Fishrock123

Fishrock123 Aug 18, 2015

Member

Same dates?

@jasnell jasnell force-pushed the jasnell:schedule-adjustment branch from 1be6bf0 to 043e2ea Aug 18, 2015
@jasnell jasnell force-pushed the jasnell:schedule-adjustment branch from 043e2ea to 6085390 Aug 18, 2015
@jasnell

This comment has been minimized.

Copy link
Member Author

jasnell commented Aug 18, 2015

@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>

This comment has been minimized.

Copy link
@rvagg

rvagg Aug 18, 2015

Member

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.

This comment has been minimized.

Copy link
@shigeki

shigeki Aug 19, 2015

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.

@shigeki

This comment has been minimized.

Copy link

shigeki commented Nov 5, 2015

@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.

@Fishrock123

This comment has been minimized.

Copy link
Member

Fishrock123 commented Nov 5, 2015

^^^^^ Just noticed this was never merged either.

@jasnell

This comment has been minimized.

Copy link
Member Author

jasnell commented Nov 5, 2015

Yes I'll get this updated but it will likely be tomorrow
On Nov 5, 2015 8:21 AM, "Jeremiah Senkpiel" notifications@github.com
wrote:

^^^^^ Just noticed this was never merged either.


Reply to this email directly or view it on GitHub
#36 (comment).

@ChALkeR

This comment has been minimized.

Copy link
Member

ChALkeR commented Jan 18, 2016

#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.)

This comment has been minimized.

Copy link
@ChALkeR

ChALkeR Jan 18, 2016

Member

Why does this PR update the actual in-tree LTS Schedule with an out-of-tree Draft schedule that has one date invalid?

This comment has been minimized.

Copy link
@ChALkeR

ChALkeR Apr 27, 2016

Member

Note: this specific change still doesn't look good to me.

@ljharb ljharb mentioned this pull request Jan 21, 2016
@MylesBorins

This comment has been minimized.

Copy link
Member

MylesBorins commented Jan 21, 2016

this just ended up on my radar, is there a reason we have not landed this yet?

@ChALkeR

This comment has been minimized.

Copy link
Member

ChALkeR commented Apr 27, 2016

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.

This comment has been minimized.

Copy link
@ChALkeR

ChALkeR Apr 27, 2016

Member

Nit: line length.

`v4.x` LTS was cut the previous year, `v6.x` will transition in to LTS and the
cycle repeats.

Let's assume (hypothetically) that the first LTS Release occurs on

This comment has been minimized.

Copy link
@ChALkeR

ChALkeR Apr 27, 2016

Member

Do we need this assumption nowdays?

@jasnell

This comment has been minimized.

Copy link
Member Author

jasnell commented Apr 27, 2016

I will work on getting this updated tomorrow

@mgol

This comment has been minimized.

Copy link

mgol commented Aug 2, 2016

Is this PR still applicable?

@jasnell

This comment has been minimized.

Copy link
Member Author

jasnell commented Aug 2, 2016

Actually, I think this can be closed now.

@jasnell jasnell closed this Aug 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.