We already have Build-Official-.* for that purpose.

Oh, I see, but I was specifically wondering about making components because they're better (for some definition of better, which I don't fully understand yet, but I was told they are, and I saw a lot of other labels, like the infra ones, turned into components, which I assume was for good reason). Can those labels be turned into components (and renamed?)?

Any opinion about making components instead of labels?

Let's just use the existing Build-* labels, we already have build-official, build-official-signing, build-official-scripts... and can extended that set as need.

I'd ultimately like to consolidate namespaces, rather than create a brand new one.  Right now we have Build and Infra, both of which are being used, two is confusing... a third makes me sad.

Regarding component versus labels, in practice it doesn't matter materially.  Components are meant for functional work categorization (e.g. Bookmarks), whereas labels are meant for broader work tracking, which potentially cuts across components.

FWIW, I wasn't looking to add yet another label/component. I would rather see the "build-official" tags renamed to "release", which I think is less confusing because "build" implies, well, building, or buildbot, and might not be the obvious thing to look for when something goes wrong with branching or merging or signing or omaha or whatever.

Would Infra>Client>Chrome>Official work?

LG, from my perspective.

I think Ben fixed this a while back (1).  Please re-open if I'm missing something.

https://bugs.chromium.org/p/chromium/components/detail?component=Infra%3EClient%3EChrome%3ERelease