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

A decision that has been rejected for various technical and business reasons

An implemented solution that has been marked as retired/obsolete

A trialing prototype that has been spiked while pending final approval for the ADR. This step is needed for complex proposal that is hard to estimate on paper.

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

Label for issues closed by script or automated processes

This issue / MR affects the AWS Cloud Platform

This issue / MR affects the Azure Cloud Platform

Merge request label for indicating cherry picks

This issue / MR affects the common code

Component related to DDMS

This label is used to indicate a MR that is a direct patch into a release branch for fixing an issue without a merge in main/master branch

This issue / MR captures a change in documentation

This issue / MR affects the Google Cloud Platform

This label is used to indicate cherry picks into previous releases for fixing an issue, this is for backporting patches in up to N-2 releases.

This issue / MR affects the IBM Implementation on Open Shift

Used on MRs that have breaking changes, therefore requiring a major version bump on the next release.

Used on MRs that have backwards-compatible new features, therefore requiring a minor version bump on the next release.

Used on MRs that have bugfixes or optimizations with no changes to features, therefore requiring a patch version bump on the next release.