New issue
Advanced search Search tips

Issue 690713 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Label Request] Stability>third-party

Project Member Reported by wfh@google.com, Feb 9 2017

Issue description

1] Label Name: Stability>third-party

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...): Stability

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: Issues related to interaction with third party code

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

Stability team will triage.

Happy for the naming to be changed as needed to fit the existing style/standard, but something including 'third' and/or 'party' would be good.


 
Labels: Stability-ThirdParty
Status: Fixed (was: Untriaged)
Added:

Stability-ThirdParty                = Third party code interactions

Sign in to add a comment