1] Label Name: Hotlist-Enterprise

Guideline 1: Unless a hierarchy of labels is needed, please avoid creating
new root parents.
Guideline 2: Proj(ects) labels should be used for efforts that have a clear
start/ end
Guideline 3: Hotlist labels should be used for tracking on-going efforts
across multiple components (e.g. Hotlist-GoodFirstBug)
Guideline 4: Due to the way auto-complete works we avoid using hyphens to
express anything other than hierarchy (e.g. UI-Browser-Omnibox).  We use
CamelCase to represent multiple words (e.g. Hotlist-CamelCase versus
Hotlist-Camel-Case).


2] Parent Label (e.g. Proj-, Hotlist-, etc...): Hotlist

Note: We generally avoid creating new component namespaces, unless there is
a new hierarchy that needs to be expressed.  Please try and use existing
label as parents.

3] Description of Label: Label used by eng + support to track bugs that impact Enterprise customers.

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently). Support and Chrome/Chrome OS Enterprise teams track these bugs. See also go/cros-ent-bug-triage