-
Notifications
You must be signed in to change notification settings - Fork 575
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
Codename for Node.js v6 LTS #118
Comments
Picking up from the conversations after last year's initial LTS, is there a good reason for keeping a name? Why not just drop it and have |
I'd go with either Barium or Bohrium, the former being my favorite. Barium
|
Beryllium is a pretty nice one too, considering it is found in emerald (the node js stone) |
From a Docker point of view the LTS code words are great since they uniquely refers to one specific LTS version and can be referenced like this:
|
At this point I'm definitely +1 on keeping the code name. Yes it can be a bit silly but there are folks who have found good uses for it. |
My recollection of the previous discussion around codenames is that we'd stick with it for now and give it a proper trial because we figured it would become more valuable when we have >1 LTS line out there. I'm still a big fan, mainly for the practical benefits but also partly to add a tiny bit of fun into the whole process. So let's try and approach it this way: which ones would you knock out and for what reason?
Strong -1 on Bromine from me because of the origin meaning. -0 on Berkelium and Beryllium for slight difficulty in reading and spelling, I'd say the same to Bohrium but I like it for other reasons. Also, I know @cjihrig has opinions here, he spoke about this @ https://youtu.be/kn0Trjl7ZRE?t=17m51s and said Boron would be a good choice because of the ease of spelling for non-native english speakers. |
That's a really interesting point Based on that I'm in favor of boron.. |
I have a very strong recollection of that only being for the first LTS, aka only v4 LTS. Please see last year's discussion: #26 -- discussed at #43 (recording, since there were no good minutes taken: https://youtu.be/wfg2nHXAQqI?t=8m15s) Going to loop in the people who didn't really (or seem to) like the idea last year: |
Going to also loop in something that @brycebaril said to me, which is quite relevant for us (NodeSource):
|
Still doesn't seem to convey anything to me. "v6 LTS" says what it is, "Boron" is a conversation on "what does that mean? Oh. It's v6 LTS." |
Android Kitkat tells you the same level of information as Node Boron. |
From our README, which we've been using as our policy document:
This was done when we changed it from our "proposed" to "current" plan on the 23rd of July 2015. I can't find any official vote on this matter. I believe it's something that was floated, got fairly enthusiastic reception both on nodejs/node and on this repo and then we received the objections from npm at the last minute before we shipped v4, as per the video @Fishrock123 linked to we decided to move on "for this release" from the objections. The closest thing for a way forward after shipping is this from @Fishrock123 @ #26 (comment):
And as with everything we do, it's open for discussion and we can do that now if folks feel strongly enough, but you'd better start making a good case for a policy change otherwise we'll have to move forward with what we have in place. |
See: nodejs/node#8026 for the voting thread. |
Since I can not comment on #127, I am posting this here. I would like the LTS wg to take into consideration that LTS code names are very useful for the official Node.js Docker Image. Since there are multiple LTS versions and they change from time to time we can not have a tag named A GitHub code search for |
Sorry @Starefossen ... that was my bad... #127 shouldn't have been locked. |
We got there! |
It's time to start working toward assigning a codename to v6 LTS! My proposal is that @nodejs/lts narrows down the list to 3 if we can, then post it to a locked thread in https://github.com/nodejs/ctc so that only Collaborators can comment, we put a comment per name and invite collaborators to vote by pinning an emoji to one of the comments.
Here's the candidate list, thanks to http://www.periodni.com/elements_symbols_sorted_alphabetically.html
Barium
Berkelium
Beryllium
Bismuth
Bohrium
Boron
Bromine
For me, the only one I'd easily strike is Bromine because of the meaning ("stench"). Berkelium, Beryllium and Bohrium all have slight problems with ease spelling from sound, but I have a soft spot for Bohrium because it was named after Bohr. Boron might trigger associations with "boring", but meh.
The text was updated successfully, but these errors were encountered: