Prepare for v4 LTS and v5

[rvagg]

From nodejs/node#3000 where this question is something to be resolved by the @nodejs/website WG:

• How do publicise and promote LTS lines? Does @nodejs/website have ideas on how to make this happen when we have something called "LTS" and then start to get new "Stable" releases with a 5 at the front? Ideally, users will be self-selecting and would end up with the kind of release suited to them, perhaps we need to outline on the front page of the website and/or on the download page why you would choose LTS over Stable?

Until the first item in the list @ nodejs/node#3000 is resolved I think you need to be prepared for the following scenarios:

1. a v5 and a v4 LTS: this will be the eventual situation no matter what but this is a possible scenario from next week onward
2. a v4 LTS only: do you do anything special for this or just treat it as yet another v4? It's possible we have this scenario next week

Also, we probably should have wording for what LTS actually means, to put somewhere, feel free to kick that over to @nodejs/lts and make them do it if you want, either open a new issue and describe exactly what you need or add it in nodejs/Release#43.

[phillipj]

Will there be changes to https://nodejs.org/dist/index.json?

[Fishrock123]

cc @nodejs/evangelism

@mikeal can we bring anyone from foundation-level marketing in to discuss this?

[rvagg]

@phillipj perhaps a lts column/field in index.json and index.tab would be good, it could include the codename for lts releases

[phillipj]

@rvagg sounds like a good plan. I'll could do some tests with that in mind for scenario 1, probably in the weekend / early next week.

For scenario 2, as long as file structures on /dist/ stays the same and we find it in index.json, no changes would be needed for us. Although adding some hard coded LTS strings around could be helpful to emphasize it, e.g. Current version: v4.x.x LTS on the frontpage

[bnb]

From an Evangelism perspective, there shouldn't be much of a problem. Weekly or twice-weekly tweets, as well as listing of updates in blog posts, are easy. However, will we be attempting to pull people in to either using or contributing to LTS? Will it have independent contributors, outside of core?

[phillipj]

Alright, to get the ball rolling I'll post some screenshots with some minimal changes necessary to host two release lines at the same time. All kind of feedback is much appreciated!

I'm thinking we should keep it as simple as possible to download the version of node most devs will use, which I've been told is stable, soon to be v5.

On the frontpage an LTS-link could been added beneath the big green download button, sending users directly to e.g. https://nodejs.org/dist/v4.2.1/.

As for the download page, a couple of links could be added to do some JS toggling of the URLs in the download matrix. An explanation of what LTS is and its pros/cons should also be added, either as a new section on the download page, or a completely new page which explains the release lines in great detail with content provided by @nodejs/lts as mentioned in nodejs/Release#44.

Any thoughts?

[jasnell]

I would much rather see the two releases side by side with clearly marked
download buttons for each rather than having LTS behind some easily
overlooked small link text.
On Oct 15, 2015 12:58 PM, "Phillip Johnsen" notifications@github.com
wrote:

Alright, to get the ball rolling I'll post some screenshots with some
minimal changes necessary to host two release lines at the same time.
All kind of feedback is much appreciated!

I'm thinking we should keep it as simple as possible to download the
version of node most devs will use, which I've been told is stable, soon
to be v5.

On the frontpage an LTS-link could been added beneath the big green
download button, sending users directly to e.g.
https://nodejs.org/dist/v4.2.1/.

[image: screen shot 2015-10-15 at 21 19 42]
https://cloud.githubusercontent.com/assets/1231635/10525570/c2808778-7385-11e5-9981-045c40c5e992.png

As for the download page, a couple of links could be added to do some JS
toggling of the URLs in the download matrix. An explanation of what LTS is
and its pros/cons should also be added, either as a new section on the
download page, or a completely new page which explains the release lines in
great detail with content provided by @nodejs/lts
https://github.com/orgs/nodejs/teams/lts as mentioned in nodejs/Release#44
nodejs/Release#44.

[image: screen shot 2015-10-15 at 21 39 14]
https://cloud.githubusercontent.com/assets/1231635/10525576/c78239d8-7385-11e5-80ec-05511653c5a1.png

Any thoughts?

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

[mhdawson]

Yes, my first preference is that if you don't choose carefully you end up with the LTS release. ie unless you know what you are doing and know that you want the latest/greatest you end up with an LTS release.

[phillipj]

I would much rather see the two releases side by side with clearly marked
download buttons for each rather than having LTS behind some easily
overlooked small link text.

Understandable. I appreciate when website are focused on the most important part(s) which should be relevant for the majority of users. On the other side, we cant really predict what our users really want before seeing the download figures, although we'll ofc influence those numbers by just having one button from the get go.

[srl295]

Could there be something user focused like: "looking for updated solid and stable? → LTS • want to try out the latest features? → latest" So try to switch based on the users self identification.

[phillipj]

Thanks for your input so far! A couple of new screenshots:

1) Two green buttons side by side

2) User oriented texts w/links

If I misunderstood your thoughts @jasnell @srl295, just say the word and I'll happily do some changes.

Anyone got a favorite amongst those two alternatives?