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.

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

Merge request label for indicating version upgrade of libs

An enhancement may be made to address specific user needs or requests, or they may be made to address broader goals, such as increasing the efficiency or effectiveness of the software. May or may not require an ADR depending on the nature of the change. This applies to improving or enhancing existing software behavior only, without introducing new features.

Label used to indicate issue found during M23 milestone

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.

Label used to indicate issue found during M22 milestone

Label used to indicate issue found during M17 milestone

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.