Issue Triaging

All issues in the ECMA-402 repository should have at least two labels: component and status.

Component labels begin with "c:" and are listed below:

• c: datetime dates, times, timezones
• c: locale locale identifiers
• c: meta intl-wide issues
• c: numbers numbers, currency, units
• c: spec spec editorial issues
• c: text case mapping, collation, properties

Status labels begin with "s:" are are listed below:

• s: blocked the issue is blocked on upstream
• s: comment more info is needed to move forward
• s: discuss TG2 must discuss to move forward
• s: help wanted help wanted; needs proposal champion
• s: in progress the issue has an active proposal

When new issues come in, the chair should assign the issue to the appropriate component. The status should start as s: discuss; the issue should discussed at the next TG2 meeting, and then either moved up to s: help wanted if the committee thinks it is a worthwhile issue, or down to s: comment if the committee is unconvinced that the issue is worth the time investment to fix (such as when the use cases are unclear).

Once a champion has been identified for a s: help wanted issue, the issue should be moved to s: in progress, and eventually closed once the corresponding proposal or PR has been checked in to the ECMA-402 repository.

s: blocked is a special status, which means that ECMA-402 is unable to move because of an underlying issue in an upstream spec (such as the Unicode spec) or library (such as ICU).