Labels - DSC-iTC/cPP GitHub Wiki

A large number of labels have been created to categorize/track Issues and Pull Requests submitted to the iTC. There are in general, 5 groupings of these labels, and combined they provide an overall way to mark an Issue or Pull Request such that it can be assigned and worked on appropriately.

Weighting Labels

The first group is used for weighting Issues. Weighting is used to determine priority for working on any particular Issue that has been submitted. These labels are all marked as:

<num><+/-> <description>

The number is the amount of weighting to be added, the +/- is whether this should be added/subtracted from the total, and the description is why the label is added.

Weighting is generally calculated based on the sum of the label values. To be clear, this means that higher values equate to higher priority (as opposed to saying 1 is the highest priority, 2 is second, etc).

NOTE: the labels are listed with the +/- second to group them together when assigning the labels (instead of all the "-" at the beginning and the "+" at the end which is how GitHub orders them).

Issue Status

There are several labels that are used for tracking progress (and are tied into the Projects, hopefully in an automated way at some point). These are:

  • Awaiting Priority
  • Awaiting Review
  • In Progress
  • Parking Lot

These labels are used to triage and track the Issue as it is worked on by the iTC.

In addition, there are some status labels for Issues that may not be worked on (and the labels reflect some of the reasoning):

  • duplicate
  • invalid
  • wontfix

Type of Request

These labels are used to specify the type of change.

  • Interpretation
  • editorial
  • enhancement - generally reserved for a completely new feature, as opposed to a change to an existing one
  • technical
  • bug - generally not used, as editorial or technical should be used instead, but if it isn't clear, this is a catchall

Applicable Document(s)

This specifies which document(s) where the initial Issue is raised. Depending on the Issue a change may be needed across multiple docs, but this is where the initial question is raised.

  • cPP
  • SD - Supporting Document
  • PP-Config

Misc

These labels don't necessarily fall into any other category:

  • question - not necessarily a change itself, could lead to a an Interpretation label
  • help wanted
⚠️ **GitHub.com Fallback** ⚠️