You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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 So I sent this simplest PR which is to update the docs in the main repo
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.
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.
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.
Activity
MylesBorins commentedon Apr 20, 2016
I'm +1 on this. Who needs to sign off on a change this big? @nodejs/tsc? @nodejs/ctc?
mscdex commentedon Apr 20, 2016
Did we decide on the name "Current?"
MylesBorins commentedon Apr 20, 2016
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 commentedon Apr 20, 2016
I like "Current"
mikeal commentedon Apr 20, 2016
@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 commentedon Apr 20, 2016
oh, also, many other projects use the term "Current" for exactly what we're using it for.
kahwee commentedon Apr 20, 2016
"Current" seems to be a better word indeed, since "LTS" is stable too.
jasnell commentedon Apr 20, 2016
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 commentedon Apr 20, 2016
I have always found our usage of
Stableproblematic and am in favor ofCurrentas a replacement.mikeal commentedon Apr 20, 2016
go ahead and prepare a PR and we can get whatever signoff necessary.
MylesBorins commentedon Apr 21, 2016
on it
MylesBorins commentedon Apr 21, 2016
@mikeal So I sent this simplest PR which is to update the docs in the main repo
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 thatThose 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.
5 remaining items
MylesBorins commentedon Apr 23, 2016
jasnell commentedon Apr 23, 2016
This only impacts the Stable branch naming, not LTS naming.
Fishrock123 commentedon Apr 23, 2016
Right, and we all know that this discussion in the past has not just touched on the stable branch. So I'd like to make sure of it.
Fishrock123 commentedon Apr 24, 2016
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.
doc: change references to Stable to Current
doc: change references to Stable to Current
doc: change references to Stable to Current
stevemao commentedon Apr 27, 2016
Can we close this since #672 is merged?
doc: change references to Stable to Current