New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 888702 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Sep 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Label Request] Hotlist-CEPartnerEng

Project Member Reported by jasonwong@chromium.org, Sep 24

Issue description

1] Label Name: Hotlist-CEPartnerEng

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: Chrome Enterprise Partner Engineering hotlist

4] Please specify what triage practices will be followed for the label
(i.e. what team will do it and how frequently).

Chrome Enterprise Partner Engineering are tracking issues and FRs filed under the Hotlist-CEPartnerEng label.


 
Status: Fixed (was: Untriaged)
Update: this request has been granted. Closing bug. 

Sign in to add a comment