How about to update the name of issue label for V8?

nodejs / CTC

Node.js Core Technical Committee & Collaborators

80 stars 27 forks source link

How about to update the name of issue label for V8? #103

Closed watilde closed 7 years ago

watilde commented 7 years ago

Currently, we're labelling V8 related issues as V8, but it potentially makes a confusion since Node.js v8.0.0 is coming around the corner. It will be necessary to clear whether V8 or v8.x or V8 in v8.x in some discussions.

Here is an actual example to imagine:

So that I'd suggest using the other name for V8 label:

V8 JavaScript Engine: used in the official blog
Chrome V8: used in the official website

addaleax commented 7 years ago

How about V8 → V8 Engine?

watilde commented 7 years ago

^The shortened name would be better :)

andrasq commented 7 years ago

In my own notes I've kept the short V8 for the engine, am using v8.x for the version.

addaleax commented 7 years ago

Fwiw that’s also how we currently use the labels. But if renaming the V8 label might help reduce confusion, why not?

MylesBorins commented 7 years ago

I thought we were dropping the v from version v8.x -> 8.x

jasnell commented 7 years ago

Yep, we are. The branches will still have the v for sake of consistency with the other release branches, but the v will be removed from the changelogs and messaging.

addaleax commented 7 years ago

Renaming labels is cheap, so it’s called V8 Engine now. If somebody else has better suggestions, we can just re-rename. :)

watilde commented 7 years ago

Closing as resolved, but what @addaleax said.

Thanks!

gibfahn commented 7 years ago

Now the github-bot is auto-labelling PRs, if we change label names we need to update the bot.

Still +1 on this change, just noting for future reference.