Skip to content
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

First LTS Release 'codename' #26

Closed
jasnell opened this issue Jul 22, 2015 · 37 comments
Closed

First LTS Release 'codename' #26

jasnell opened this issue Jul 22, 2015 · 37 comments

Comments

@jasnell
Copy link
Member

jasnell commented Jul 22, 2015

@nodejs/lts ... please offer candidates for the codename for the first LTS release.

as far as I'm concerned, the obvious first choice is hydrogen.

@Fishrock123
Copy link
Contributor

hydrogen and chromium overlap with v8/chrome. (hydrogen is v8's debugging output.)

I suggest we should never term one of our releases those because it will be very confusing.

I'm honestly not sold on elements, but I also don't have great suggestions. Maybe color?

@jasnell
Copy link
Member Author

jasnell commented Jul 23, 2015

I'm not particularly concerned with possible overlap in the naming. It should be clear through context that the names refer to very different things.

@rvagg
Copy link
Member

rvagg commented Jul 23, 2015

I had the same concern as @Fishrock123 about Hydrogen which is why I've steered clear of it in suggestions, but also I agree that context makes this less of a concern.

I was quite attracted to the idea of using the noble gasses, they are all pretty awesome. Node.js Helium, Node.js Neon.

Then there's line 6 of the periodic table which has some of the best names: Cae­sium, Ba­rium, Lute­tium, Haf­nium, Tanta­lum, Tung­sten, Rhe­nium, Os­mium, Iridium, Plat­inum, Gold, Mer­cury, Thallium, Lead (maybe not), Bis­muth, Polo­nium, Asta­tine, Radon

@jasnell
Copy link
Member Author

jasnell commented Jul 23, 2015

I'm good with using the Noble gases. Helium is good start.
On Jul 22, 2015 6:29 PM, "Rod Vagg" [email protected] wrote:

I had the same concern as @Fishrock123 https://github.com/Fishrock123
about Hydrogen which is why I've steered clear of it in suggestions, but
also I agree that context makes this less of a concern.

I was quite attracted to the idea of using the noble gasses, they are all
pretty awesome. Node.js Helium, Node.js Neon.

Then there's line 6 of the periodic table which has some of the best
names: Cae­sium, Ba­rium, Lute­tium, Haf­nium, Tanta­lum, Tung­sten,
Rhe­nium, Os­mium, Iridium, Plat­inum, Gold, Mer­cury, Thallium, Lead
(maybe not), Bis­muth, Polo­nium, Asta­tine, Radon


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

@Fishrock123
Copy link
Contributor

I'm just going to vote we start at Ununoctium.

@thefourtheye
Copy link
Contributor

Crazy idea: I propose actual first names of people based on their number of commits. Maybe we can start with Node.js - Ryan?

@Fishrock123
Copy link
Contributor

Also: Lithium is also used somewhere in v8-related things. (grep the log when you build)

@lfortin
Copy link

lfortin commented Aug 26, 2015

Other idea:

Node.js release codenames could be based on corresponding element atomic number:

v4 : Beryllium
v5 : Boron
v6 : Carbon
v7 : Nitrogen
v8 : Oxygen
v9 : Fluorine
v10: Neon
...

@srl295
Copy link
Member

srl295 commented Aug 26, 2015

Lead (maybe not)

Plumbum

@trevnorris
Copy link

Node.js release codenames could be based on corresponding element atomic number:

Since LTS is only every even release would be skipping half the elements.

@paulvi
Copy link

paulvi commented Sep 22, 2015

Both Android and Eclipse use first letter corresponding to order in ABC, then Android follows sweets theme while Eclipse follows astronomy theme.

v1 A  
v2 B  
v3 C  
v4 D  
v5 E  
v6 F  
v7 G
v8 H  
v9 I
v10 J  

etc

There should be just a word starting from that letter.

This way after couple of years and dozen of version passing, any one can still easy figure out what numeric version goes for H* or B* codename.

If you stick to chemical elements, take a look at http://www.periodni.com/elements_symbols_sorted_alphabetically.html

@Slayer95
Copy link

Protium :)

@mikeal
Copy link
Contributor

mikeal commented Sep 22, 2015

"Hartnell" named for the first actor playing Dr Who.

That gives us twelve more easy choices before moving on to a new naming scheme :) https://en.wikipedia.org/wiki/Doctor_Who

@ceejbot
Copy link

ceejbot commented Sep 22, 2015

Hartnell, Troughton, Pertwee, Baker, Davison, Baker, McCoy, McGann, Hurt, Eccleston, Tennant, Smith, Capaldi. There's a Baker collision that you can resolve with TomBaker vs ColinBaker. Heh.

@djensen47
Copy link

Male actors' names? 👎

@lennym
Copy link

lennym commented Sep 22, 2015

I can't help but think that whatever naming scheme is used, it should be possible to compare versions by inspection, by which I mean without any additional knowledge, be it the periodic table or the succession of actors playing The Doctor.

I don't think it's coincidence that almost all other similar schema use alphabetic names on a theme.

@mhdawson
Copy link
Member

+1 on using something alphabetic

@rvagg
Copy link
Member

rvagg commented Sep 22, 2015

@djensen47
Copy link

I though the periodic table is off the table because of collisions with V8, no?

@djensen47
Copy link

Fruit? These are, for the most part, common but you can always find more exotic alternatives:

Apricot, Blueberry, Cranberry, Durian, Elderberry, Fig, Guava, Huckleberry, Imbu, Jackfruit, Kumquat, Lychee, Mango, Nectarine, Orange, Papaya, Quince, Raspberry or Rumbutan, Strawberry, Tamarind, Ugli fruit, V, Watermelon, X, Y, Z

@paulvi
Copy link

paulvi commented Sep 23, 2015

👍 second @djensen47 Dave for fruit

@Pierre-Gilles
Copy link

Matrix characters ? :D ( Trinity, Morpheus, Tank, Dozer, Smith, Apoc, Jones, Brown )

Otherwise, more seriously, mythological figures :

Hyperion, Atlas, Aura, Asteria, Helios, Pallas, Styx, Clymene, Persephone, Pontos, Triton, Loxo, Harmonia , Gelos...

( full list here : https://en.wikipedia.org/wiki/List_of_Greek_mythological_figures )

@jasnell
Copy link
Member Author

jasnell commented Sep 23, 2015

Node v4.0.0 'Bikeshed'

@Fishrock123
Copy link
Contributor

Node v4.0.0 'Bikeshed'

Oooh burn!

.. Did we already settle on the periodic table way back when? I still suggest colors.

@jasnell
Copy link
Member Author

jasnell commented Sep 23, 2015

We had a rough "consensus" to use the periodic table largely because I don't believe we had any better ideas. I still don't ;-) ... however, one idea that struck me would be to use the names of cities around the world, without any bias given to any particular geopolitical region or state -- perhaps an alphabetized sort of the most populated cities (https://en.wikipedia.org/wiki/List_of_cities_proper_by_population). Abidjan would appear to be the first from the sorted wikipedia list.

@djensen47
Copy link

Did we already settle on the periodic table way back when? I still suggest colors.

I like colors as long as they are somewhat uncommon and/or multisyllabic:

  • Aquamarine
  • Black Coral
  • Carnelian
  • Desert Sand
  • Eggshell
  • Fuchsia

And so on …
https://en.wikipedia.org/wiki/List_of_colors:_A%E2%80%93F
https://en.wikipedia.org/wiki/List_of_colors:_G%E2%80%93M#Colors
https://en.wikipedia.org/wiki/List_of_colors:_N%E2%80%93Z#Colors

@djensen47
Copy link

The Node.js logo is a shape, a hexagon. So what about shapes:

  • Acute Triangle
  • Buckyball
  • Circle
  • Dodecagon
  • Equilateral (Triangle)
  • Gomboc

Okay, I'll stop now. 😄

@srl295
Copy link
Member

srl295 commented Sep 24, 2015

Side note: whatever genre, we could expand into other translations such as colores or elementos

If we go with "bikeshed" it could be l'abri à vélos, fietsenschuurtje, cykelställsfråga, skkţ hʼwpnyym ( transliterated- stay with Latin or possibly ASCII?)

@rvagg
Copy link
Member

rvagg commented Sep 29, 2015

@nodejs/lts: if we can figure this out this week we'd be better placed to get feedback from collaborators before v4 LTS lands. Any active @nodejs/lts members want to propose a way forward?

@zkat
Copy link

zkat commented Sep 30, 2015

How about...

..."Four point oh point oh", conveniently shortened to v4

@aredridel
Copy link

<3 integers.

@zkat
Copy link

zkat commented Sep 30, 2015

Alternately:

  • Who
  • What
  • I Don't Know
  • Why
  • Because
  • Tomorrow
  • Today
  • I Don't Give a Darn
  • Nobody
  • Verisimilitude

@isaacs
Copy link

isaacs commented Sep 30, 2015

Yeah, +1 on not using cutesy names. We have semver. It's super duper clear. Code names are good for stuff you don't want people to understand, like secret military plans, or Apple products. It can only cause harm, imo.

@tamzinblake
Copy link

+1 on naming it a semver.

@Fishrock123
Copy link
Contributor

@issacs Could you clarify? It will be versions as it currently is from stable (I.e. 4.2.x) but a code name is something to associate with for the long term, mostly to help people remember which one.

@isaacs
Copy link

isaacs commented Oct 6, 2015

@Fishrock123 I usually find codenames make conversations about support levels and versions a lot harder to keep clear, once there are a few of them in place. (Did Tiger come before Snow Leopard? Or am I thinking of Mountain Lion? Is El Capitan newer than Mavericks? Isn't El Capitan at Yosemite? Are we doing mountains or cats or surfing locations?)

If we say that 4.x is the long-term supported version, and so is 6.x and 8.x (for example), then there's no confusion about whether Isotope is functionally equivalent to Rutabega or lacks the features in Sun Lamp.

But, I'm also of the opinion that this is a bikeshed, and the best way to settle a bikeshed is to appoint a dictator for that decision, and just do whatever they say, rather than debate it.

@Fishrock123
Copy link
Contributor

Ok so, the reality is (as was discussed in the latest lts meeting) we've been saying we are going to have one since the beginning of the LTS discussion, and so we are going to just go with one now since we're only like a week out. As such, it's a bit late to be discussing this. We can re-evaluate if it was useful or not for the second LTS. :)

Going to close this now since nodejs/node#3212 is up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests