Pick the next ten codenames or something like that #317
Comments
|
Oh, and once picked, publish, of course. |
|
Here's my suggestion. Rubber-stamp it and I'll PR it into a document.
By this point, we'll have hopefully decided to stop with the elements theme and let go of all the problems it entails: Many letters not represented, irksome to avoid poisons etc., often difficult or impossible to get a name that is familiar to the average English speaker ("Isn't Dubnium a music genre that is always at 114 bpm? Erbium? Was that named after Airbnb?")... Maybe we can make a tradition of switching themes halfway through the alphabet every time. |
|
Those code-names sound good enough for me. A rose by any other name... Specially if there is no conclusion on #127, or if conclusion is for the status-quo (continue using code names), I would much prefer that we decide the names upfront, instead of drowning out release planning conversation with bike shedding on the code name. |
|
No objections here to those names. |
It's cool that it isn't too late to switch theme now. I even think that it's better to switch it now than in 2025. I don't know how this theme was chosen, but feels like it wasn't thought for these problems back then. But anyway, i'm not against anything :) Just 2c. |
|
@Trott ship it |
|
+1 from me on the proposed codenames. |
|
|
@Trott Slight caveat w.r.t. Gold: could be misconstrued as saying something about the version (gold master, …). Alternative: Gallium |
|
While I'm fine with the general idea, I'd prefer for 10.x to be the last of the element named lines and to pick a different theme for 12.x and on. And if we can agree to a new theme in time, I'd prefer to use a different name for 10.x also |
|
@jasnell Has your last comment something to do with the fact that it's the 1st of April? |
|
Not at all. |
|
Why change from elements? Why go with an inconsistent naming theme? Why introduce inconsistency for something that is, ultimately, not that important. And I support Gallium over gold. Gold does have unique connotations. Other than that, be bold...be daring...accept the list and move on. |
|
More for future reference: |
PR-URL: nodejs#318 Fixes: nodejs#317
|
@jaredreich in line with the characters in the seminal science-fiction series Sapphire & Steel I propose including gemstones, alloys and other compounds for J, Q and W where necessary. |
|
Maybe consider cool-sounding compounds that are solid at room temperature for LTS releases and liquid at room temperature for the rest? |
As proposed by @ofrobots: It would be great if @nodejs/Release could select and publish the next 3, 4, 5, 10, 100 codenames so that we don't have a big discussion every time a destined-for-LTS release comes around. See #291 for a pretty good example of how out-of-hand this gets. Maybe it's just me, maybe this sort of discussion is fine, but I think it runs the risk of burying pretty much any other topic that needs to be talked about in a release.
Not sure if Release WG rules allow me to put this on the meeting agenda, but I'll label it as such and hope the answer is "yes". (There are Release-agenda and lts-agenda labels. Not sure if there's a difference.)
The text was updated successfully, but these errors were encountered: