-
Notifications
You must be signed in to change notification settings - Fork 579
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
Node.js 10.0.0 Tracking #291
Comments
+1 |
Ping @nodejs/release @nodejs/lts @nodejs/tsc .@nodejs/collaborators.. Because Node.js 10.x will be an LTS branch, it needs an LTS code name. The 8.x code name was "Carbon", which means we're on the D's. Unfortunately, the options for
Aside from the horrible names, it would be exceedingly funny to name a Long Term Support line after either an element that decays in thousandths of a second, or after a highly unstable element, so either of the first too automatically get my vote. Please weigh in on your choice. |
My vote is none of the above. Let's pick another theme :). |
aww ;-) |
??? Diamond !!! it's not an element all right, but it's a nice shape of carbon... |
Deuterium? |
The element system will eventually fall apart as there are not elements for
every letter.
It might be worth considering another naming scheme
…On Jan 9, 2018 8:03 PM, "Trivikram" ***@***.***> wrote:
Deuterium <https://en.wikipedia.org/wiki/Deuterium>?
It has a number of commercial and scientific uses, like nuclear reactors,
spectroscopy, tracing, drugs etc
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV4GuxOfvRHxBEi1dFhslfyvBpsEOks5tJAxigaJpZM4QtdbG>
.
|
Sure. Any suggestions? |
Is there actual value in still having a naming scheme? The numbers seem to be used basically everywhere. |
Animals
Comic book characters
Cities
Spices
Movie titles
…On Jan 9, 2018 8:14 PM, "James M Snell" ***@***.***> wrote:
Sure. Any suggestions?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV2eT_bjQpp-VscEDBF7tscrd2Iw_ks5tJA7ygaJpZM4QtdbG>
.
|
|
|
Come on... Fhqwhgads
…On Jan 9, 2018 9:52 PM, "Rich Trott" ***@***.***> wrote:
- Muppet characters (Animal, Beaker, Camilla, Dr. Teeth...)
- Homestar Runner characters (Arrow'd Guy, Bubs, The Cheat, Drive-Thru
Whale, Fhqwhgads...)
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV4Dm03HpE9djxNd3MItYpBk-HL8lks5tJCYBgaJpZM4QtdbG>
.
|
Positive Words That Start With DDABBLE, DAIMON, DAINTIFY, DAINTY , DANCE, DANCER , DANDY, DANKE, DANKEN, DAPPER , DAPPERLY, DARING , DARINGLY, DARLING , DASHING, DASHINGLY , DAUNTLESS , DAUWTRAPPEN, DAWN, DAYEE, DAZZLE, DAZZLED, DAZZLING, DAZZLINGLY , DEAD-CHEAP, DEAD-ON, DEAN , DEAR , DEAR ME, DEARLY, DEBONAIR, DEBONAIRLY , DECENCY , DECENT, DECENTLY , DECIDING , DECISIVE , DECISIVELY, DECISIVENESS, DECK, DECLARE, DECOCT, DECORATE, DECORE, DECOROUS, DECOROUSLY , DECREE, DEDICATED, DEDUCE, DEDUCTIVE, DEED, DEEP , DEEPEN, DEEPER PART OF YOU, DEEPLY, DEFEAT, DEFEATING, DEFENCELESSNESS, DEFEND, DEFENDER, DEFER, DEFERENCE, DEFIANT, DEFIANTLY , DEFINE, DEFINITE , DEFINITELY, DEFINITIVE, DEFIX, DEFT, DEFTLY , DEIFY, DELECTABLE , DELECTABLY , DELECTATE, DELIBATE, DELIBERATE, DELIBERATELY, DELICACY, DELICATE , DELICATELY , DELICIOUS, DELICIOUSNESS, DELIGHT, DELIGHTED, DELIGHTEDLY, DELIGHTFUL , DELIGHTFULLY , DELIGHTFULNESS, DELIVER, DELUXE, DEMOCRATIC, DEMONSTRATIVE , DEMULCE, DEMULCENT, DEONERATE, DEOPPILATE, DEOSCULATE, DEPENDABILITY, DEPENDABLE , DEPENDABLY , DEPICT, DEPOSIT, DEPREICATE, DEPURATE, DEPUTE, DEPUTIZE, DERIVE, DESCRIBE, DESCRY, DESERVE, DESERVEDLY, DESERVEDNESS, DESERVING , DESERVINGLY , DESERVINGNESS, DESIGNER , DESIRABLE , DESIRABLY, DESIRE, DESIRED, DESIRING, DESIROUS , DESTINED , DESTINY, DESUME, DETACHABLE, DETACHMENT, DETECT, DETERMINANT, DETERMINATE, DETERMINATION, DETERMINE, DETERMINED , DETERMINEDLY , DEVELOP, DEVELOPED , DEVELOPING , DEVISE, DEVISEE, DEVISOR , DEVOTED, DEVOTEDLY, DEVOTEDLY , DEVOTEE, DEVOTION, DEVOTIONAL , DEVOUT , DEVOUTLY , DEW, DEXTERITY, DEXTEROUS, DEXTEROUSLY , DIADEM, DIALECTIC, DIAMOND, DIAMONDIZE, DIDACTIC , DIE-HARD, DIFFERENCE, DIFFERENT, DIFFERENTLY , DIG, DIGHT, DIGNIFIED , DIGNIFY, DIGNITY, DILIGENCE, DILIGENT , DILIGENTLY , DIMPLE, DING, DINKUM , DIP, DIPLOMATIC , DIPLOMATICALLY , DIRECT , DIRECTION, DIRECTLY , DIRECTOR, DIRT-CHEAP, DISARMING , DISARMINGLY, DISCERNING, DISCERNINGLY, DISCIPLE, DISCIPLINE, DISCIPLINED , DISCLOSE, DISCLOUD, DISCOVER, DISCOVERER, DISCOVERY, DISCREET , DISCRETE , DISCRETELY , DISCRETION, DISCRIMINATING , DISCRIMINATINGLY, DISCUMBER, DISCUSS, DISENCHANT, DISENSLAVE, DISENTANGLE, DIS-IDENTIFY, DISILLUSION, DISINVOVLE, DISNEY, DISPAND, DISPASSIONATE, DISPATCH, DISPENSE, DISPLAY, DISSOLVE, DISTINCT , DISTINCTION, DISTINCTIVE , DISTINCTIVELY , DISTINGUISHED , DISTINGUISHING, DISTRACTING, DISTRIBUTE, DISTRIBUTOR, DIVERSE , DIVERSELY , DIVERSIFIED, DIVERSITY, DIVERTED, DIVERTING , DIVINE , DIVINE LOVE, DIVINE MAGNIFICENCE, DIVINE SIGHT, DIVINE SOUL, DIVINE VOICE, DIVINE WILL, DIVINE WISDOM, DIVINELY, DIZEN, DO, DOABLE , DOCUMENT, DOER , DOES THE TRICK, DOGGONE, DOLL, DOMINANT , DOMINATE, DOMINATED, DOMINATES, DONATE, DONEE, DONOR, DOPE, DOPE CHILL OUT, DOTE, DOTE ON, DOTED ON, DOTING , DOTINGLY, DOUBTLESS , DOUGHTY , DOVELIKE, DOVETAIL, DOWN TO A FINE ART, DOWN-TO-EARTH, DOYEN, DOYENNE , DRAFT, DRAPE, DRAW, DRAWS ME BACK, DREAM, DREAMBOAT , DREAMILY, DREAMLAND, DREAMY , DRESS, DRIB, DRINK, DRIVE, DRIVEN , DRIVING , DROLL, DROOL, DROP DEAD GORGEOUS, DUB, DULCET, DULCIFY, DULCORATE, DUMBFOUNDED, DUMBFOUNDING, DUMMY-PROOF, DUPLICATE, DURABLE , DURABLY , DUTIFUL , DUTY, DYE, DYNAMIC , DYNAMICALLY, DYNAMITE, DYNAMO |
Dragonfly |
My first thought was also Diamond. While not an element, it is a configuration of carbon. I also thought to skip to E, but E doesn't have any good (non-radioactive) choice either. So a new theme does make sense. Geographic locations are probably safe wrt trademark, but ianal. |
We likely should only use ideas that we can complete an alphabet with. Some of these are a stretch, but it is fun how many cultures are represented Herbs + SpicesDill |
@hashseed Oh, interesting idea. Maybe we could name each release after a city from a country for which we have localization support. It'd be a great way to celebrate the diversity of our community. 😊 |
Capitol CitiesAlgiers |
Node.js 14 LTS "Garlic" 🤨. I could get onboard with Ginger. Also "quatre epices" just means "four spices". I'd also like to pitch animals. But Ubuntu already has that. Or trees. Stable. Douglas, Eucalyptus, Fir, Gingko, Hazel, Ironwood, Joshua Tree, ... |
FWIW Xi'an used to be a historic Chinese capital. |
Capitals is too politic IMO. Other than fun, is there any reason we need a code name to begin with? (+1 on trees) |
Hot peppershttps://www.cayennediane.com/big-list-of-hot-peppers/ Node.js 10 "Dragon's breath" |
Mythical anymals, |
I do think it's worth noting that we can make the decision to avoid selecting names in alphabetical order with whatever we choose next - that does seem to be the downfall of the Elements option. 😊 |
+1 to:
|
Or we could simply arbitrarily skip letters. As long as the list is monotonically growing and the element has a stable isotope we are fine? Dysprosium would actually work. We could also skip to Erbium or Europium. Then there is Flourine, Gold, Helium/Hydrogen... We could also choose mineral names or gems. |
Not sure about comic book characters. Those names may be
copyright/trademark-encumbered.
jerryscript-project/jerryscript#2013 (comment)
|
I also like the idea of just using Deuterium since it’s pretty much “close enough” to being an element, and more importantly, its name sounds like it is one. (Or maybe Dilithium 😉.) |
+1 for Dilithium. Totally missed out on Adamantium, but we still got Kryptonite, Tiberium, Unobtanium and Vibranium. |
Chrome doesn't have code names btw :) |
+1 for filling in with Dahl. He isn't an element, but he was a catalyst! |
@Trott Yes. But. It's always better to have name and best practice of article writers should be to always use codenames for titles.
Yea, it's (almost) obvious - chrome, google and personalization. But even if not that, it won't be that way for long. I almost never searched or was interested or commented on 0.10 but it always appears in top places. One more example is that we all have own names, you don't refer to someone by his age (similar to versions?). Here comes one more idea. Each even version (or even more each major) to have some (single-word) name and when LTS starts - to have two-words name. Similar to what @goloroden suggested. For example, i really like the That way it's guaranteed that when you refer to the two-words name you are talking about LTS release. I strongly believe that it will help in community forums like StackOverflow and such. And also it's guaranteed that you won't mess with any versions at all. Versions are developer things. Yes, users of Node are developers too, but there are any kind of developers - junior, advanced, senior and etc, each one at different level of skills and at different sphere of JavaScript and web development at all. I think 1-2-3 characters numbers are also more error prone than codenames. @hashseed, i can bet it's because the shorter release cycle and not only of course. Here, our cycle is different and absolutely make sense every version to have codename and always to use names. Node's release plan is one of the best i've seen, along with Ubuntu's of course. @WaleedAshraf, nah.. DC's Batman. :D Marvel fan here. Stan Lee is damn freaking incredible, I just still can't believe ;d Just kidding.
What's the problem. Even if we name every version, still don't see the problem. There are billions of words out there :D |
@olstenlarck FTR, duckduckgo.com search for Anyway, I'm not opposed to codenames as much as I'm not so sure codenames should take up a ton of time and space in issues like this one. An inflexible/deterministic way to provide codenames would be great, just so we could avoid all the "I love Diamond"/"-1 to Diamond!" conversations. "Our methodology says the codename will be Dumbledore Dumpster. No, we won't change it. No, we won't talk about better names." Another possibility is to redirect all conversation around codenames to a relevant discussion board and leave it to CommComm or Release team to pick one at a specific time/date after reviewing the relevant conversation. |
I would like to propose that a designated team (perhaps @nodejs/lts) pick the next 10 or so codenames upfront, so that we can have all the 🚲🏠in one place in one shot. |
Hopefully more than 10; or at least, let’s make sure the next 1000 are something that’s merely bikesheddable. |
If not, this needs to be corrected, as after retwitting by Axel Rauschmayer (@rauschma) this will start spreading. |
@vsemozhetbyt yes it is true. See #318 and #317. |
No, it's not true in the sense that the name is not yet finalized. @Trott is making a proposal that has not yet been accepted. I'm sure we'll finalize on it relatively soonish. We do have several more weeks until the release is actually cut and 6 more months until a name is actually needed. |
Saw this proposed and accepted. Geez, folks? This should be trivial. This shouldn't be an issue, at all. Axel's concern about gold is on point #317 (comment), but for the rest? It's just names. Not even offensive names. Accept them and move on already. Drive a stake into the ground and say you're done. Especially since the choice of dubnium can also be seen as honoring the first African-American to contribute to science of element identification. And it was his birthday last week. https://twitter.com/curiouswavefn/status/978385311615959040 One thing you all need to stop doing is dithering about issues that are not that consequential, because what does that say about issues that are important? And you also need to start talking publicly about Node v10 so it's not just a figurehead milestone on a chart. Coming out with the codename is an excellent start. |
Heads up: there will be another test build of 10.0.0 coming on Tuesday April 3rd. |
@jasnell I recall seeing somewhere that Node.js 10 target release date was April 10th, but can't seem to find that context again now. Is that accurate, or am I totally making that up in my head? 😅 |
April 24th
…On Wed, Apr 4, 2018, 11:21 Tierney Cyren ***@***.***> wrote:
@jasnell <https://github.com/jasnell> I recall seeing somewhere that
Node.js 10 target release date was April 10th, but can't seem to find that
context again now. Is that accurate, or am I totally making that up in my
head? 😅
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#291 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAa2eUKkr4VHXS9Php9iYpPcAOXi8heYks5tlQ8LgaJpZM4QtdbG>
.
|
Thanks for confirming. The V8 team is relying on the fact that we have some time between V8 6.7 branch point and the Node.js 10 initial release. |
I had been planning to cut a new test build yesterday but that got delayed. I'm going to be updating the branch this afternoon and generating the test build this afternoon. |
/cc @psmarshall |
Question: given that |
@AyushG3112 I did some initial testing with it in our CI infra using an early version in a container. When it goes live and our infra providers make it available we'll be adding it to the mix and dropping 17.10. There aren't expected to be any problems with 18.04 support. |
@rvagg got it, thanks! |
I know it may be a bit late to throw my hat in to the ring regarding the name, but what about Dolomite, "the tough black mineral that won't cop out when there's heat all about"? It's also an "anhydrous carbonate mineral" according to wikipedia |
Yea, probably too late for that, but welcome to the awesome world of the geography (everything, everywhere around us) :D |
This issue can be closed now. The release is coming out tomorrow. |
|
FYI... I will be kicking off the process for Node.js 10.0.0 the first week of January. Current plan is to create the actual
v10.x
andv10.x-staging
branches on March 1st.The text was updated successfully, but these errors were encountered: