Re-brand "Stable" channel to "Current"

[mikeal]

There's been pretty wide agreement that we should do this for some time, we should pull the trigger before the v6 release.

[MylesBorins]

I'm +1 on this. Who needs to sign off on a change this big? @nodejs/tsc? @nodejs/ctc?

[mscdex]

Did we decide on the name "Current?"

[MylesBorins]

fwiw I'm +1 on a change... I'm up for whatever and will avoid getting into the naming bike shed.

"Stable" in particular has been causing some misconceptions.

[evanlucas]

I like "Current"

[mikeal]

@mscdex we have several other threads, mostly around the LTS branding, where we talked about this. A lot of those threads are side tracked by proposing re-branding LTS (which we decided not to do and survey results show that people actually do understand it pretty well) but having "Stable" and "LTS" is still confusing especially when it just isn't accurate.

[mikeal]

oh, also, many other projects use the term "Current" for exactly what we're using it for.

[kahwee]

"Current" seems to be a better word indeed, since "LTS" is stable too.

+1 because 'stable' is confusing. LTS is 'stable' too

also i have a bit of free time, so once this is signed off, can i make the PR?

[jasnell]

This is fine. I can add this into the release but since v6 is going out before the next CTC call we'll need to get agreement here. /cc @nodejs/ctc

[Trott]

I have always found our usage of Stable problematic and am in favor of Current as a replacement.

[mikeal]

go ahead and prepare a PR and we can get whatever signoff necessary.

On Apr 20, 2016, at 2:46PM, 59 notifications@github.com wrote:

also i have a bit of free time, so once this is signed off, can i make the PR?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #669 (comment)

[MylesBorins]

on it