doc: change references to Stable to Current

[MylesBorins]

Checklist

• Update website
  • Rename 'Stable' release to 'Current' nodejs.org#672
• update redirect for build
  • www: redirect from '/<lang>/downloads/stable' to '/<lang>/downloads/current' build#399
• Update LTS repo copy
  • doc: change stable to current Release#98
• Update LTS Graphic
  • Updated LTS image. Release#97
• Update https://github.com/rvagg/changelog-maker
  • Rename Node.js "Stable" releases to "Current" changelog-maker#38

Notes

With v6 we plan to rename the Stable release line to Current.
This commit updates all references to Stable in the codebase. It will
have to land along side updates to other repos within the org.

ref: nodejs/nodejs.org#669

[jasnell]

LGTM

[MylesBorins]

/cc @nodejs/ctc

[evanlucas]

I think changelog-maker will need an update too if I am remembering correctly

[MylesBorins]

From my comment in nodejs/nodejs.org#669

We will also have to update the site, I think it might make sense for @fhemberger to handle that or at least someone more familiar with the code base as the word "stable" is used not only in the copy, but in css selectors and hard coded within the tests. That being said I think we should get 100% sign off before that work is done.

As far as I can tell there is nothing that needs to be updated in /download, but perhaps someone from @nodejs/build can verify that for me.

We will also have to update the copy in https://github.com/nodejs/lts

Turns out there is only a single reference to stable, but we'll need to also update the graphic (do you know where that lives @mikeal?). If I can get a copy of a psd or illustrator file I can update that

Those are just the references I knew off the top of my head, I'll do a more in depth search after we get sign off.

edit: I'm making a checklist in the top comment. Other collaborators please feel free to edit my comment and add more to the list

[MylesBorins]

@evanlucas afaik changelog maker is agnostic to release lines. The title of the changelog is always made manually afaik

[evanlucas]

It breaks https://github.com/rvagg/changelog-maker/blob/master/groups.js#L19 (the --filter-release flag)

[MylesBorins]

PR has come in at a first pass to updating the website nodejs/nodejs.org#672

[fhemberger]

PR for changelog-maker: nodejs/changelog-maker#38

[Fishrock123]

With v6 we plan to rename the Stable release line to Current.

We do?

[MylesBorins]

There was another thread where there seemed to be consensus. Tbqh the language is written for the commit if it lands. I copied it over to the PR. I should have likely switched to more democratic language in the issue.

[Fishrock123]

I have voiced my concerns at nodejs/nodejs.org#669 (comment)

We need to make sure we give the large changes more time and not just cram them in before breaking releases...

Speaking of which, this doesn't actually have to be done in a breaking release at all. I'd rather everyone be good with it and change it afterwards than not.

[evanlucas]

This probably needs CTC approval?

[Fishrock123]

@evanlucas at the very least, I think.

[Fishrock123]

Thinking about this more in nodejs/nodejs.org#669 (comment)

Ok. I definitely think we should really take this past evangelism/marketing. I'm afraid a shift without warning may rub off on downstream customers badly and people may be increasingly hesitant about things if we do it with no prior publicly communicated indicator.

[jasnell]

Getting ctc review and encouraging input from the collaborators is exactly why this PR was opened :-)

[Trott]

@Fishrock123 wrote:

I definitely think we should really take this past evangelism/marketing.

@nodejs/evangelism @nodejs/website

[mikeal]

CTC should weigh in but it would be good to have the website change ready
for the v6 release.

On Saturday, April 23, 2016, Rich Trott notifications@github.com wrote:

@Fishrock123https://github.com/Fishrock123 wrote:

I definitely think we should really take this past evangelism/marketing.

@nodejs/evangelism https://github.com/orgs/nodejs/teams/evangelism
@nodejs/website https://github.com/orgs/nodejs/teams/website

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#6318 (comment)

[jasnell]

Need to know today if we're going to use the new naming for v6

[ChALkeR]

2016-04-26 (note the 0).

[ChALkeR]

This does LGTM (with a nit).

The only concern that I have here is that we would actually have LTS, Current, Maintenance, and Stable, at least in the changelog. We should make sure that the renaming is clear and that people can look up what did Stable mean. Perhaps we could add a line that Current was previsously named as Stable to the Readme?

[evanlucas]

LGTM with @ChALkeR's nit addressed

[fhemberger]

PR for download page redirect: nodejs/build#399

@thealphanerd Can you please update the original post?

[jasnell]

@nodejs/ctc ... I need a final Go / No Go on making this change in this release. @Fishrock123 has voiced an objection. Need to know what to use for this release.

[fhemberger]

@jasnell Website has already been updated: nodejs/nodejs.org#672 (comment)

[jasnell]

Ok... that settles it then lol. @thealphanerd can you make sure this PR is up to date and get it landed?

[jasnell]

Landed in 29a6c7c