A decision that has been approved for an ADR, issue needs to be accompanied by Progress label KB::In Progress, KB::Done

A proposed solution for an issue that requires deliberation and changing of existing behavior

This label highlights that unit test cases are being written for the issue

The ADR has been raised in the community and respective contributor members have been notified to provide feedback and reviews.

This label marks the successful merging of the code into the master branch

This label signals that a merge request (MR) has been raised to the master branch

An Architectural Decision Record (ADR) is a result of an issue backlog on feature request/enhancement, defect fixing, or a new OSDU standard that has triggered the need for a new design (perhaps requiring new technology selections, architecture patterns)

This label identifies issues that require documentation to be created or updated

Issue regarding work related to code clean ups/refactoring/optimization

This label highlights the issue is being actively worked on by the development team.

This issue relates to improving or introducing unit testing, integration, or automation in code testing

This label denotes that Preship testing in the Preshipping environments(GC/AWS/Azure/IBM/RI) is underway.

Issue life cycle label: Label applied to indicate that issues are confirmed, but no active work are in progress. Pending volunteers to pick up.

This label indicates that primary testing in the development environment is in progress. The Primary developer is conducting initial testing in the development environment.

Merge request label for indicating CICD related / DevOps changes for release management

This label denotes that secondary testing in the development environment is underway. Secondary developer (or QA) is performing additional testing in the development environment.

Merge request label for indicating version upgrade of libs/dependencies

This label signifies that the code is undergoing Final review stage and it will be approved once it is good to go

Merge request label for indicating fix for defect, software error, unintended behavior, flaw or fault within the code

This label indicates that the code is undergoing peer code review and it will be approved once it is good to go

Merge request label for indicating new feature change, generally requires accompanying ADR

Merge request label for indicating work related to code clean ups/refactoring/optimization

Merge request label for indicting changes for unit, integration, etc. testing

Catastrophic issue identified - Severe impact, contain breaking workflow/data loss, zero-day/critical security vulnerabilities No workaround and should be fixed as an immediate priority Need to be released as a patch during regular milestone cycle as soon as a fix is available

Major issue identified - High impact, might contain breaking workflow/data loss, critical/high security vulnerabilities There is a workaround that exists but should be fixed as the next priority Might need to be released as a patch during regular milestone cycle/N+1 milestone release

Minor issue identified - Low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists Can be released in N+1 or more milestone releases

Serious issue identified - Medium impact, no breaking workflow/no data loss, high/medium security vulnerabilities There is a workaround that exists and should be fixed after high priority Can be released in N+1 milestone release