This issue / MR indicates that the issue / code changes presents a breaking change, potentially affecting compatibility or existing functionality. A mitigation strategy must be communicated, providing guidance on how to adapt or resolve the breaking change for affected users or systems.

Used on MRs that have bugfixes or optimizations with no changes to features, therefore requiring a patch 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 breaking changes, therefore requiring a major version bump on the next release.

Label used to indicate issue found during M23 milestone

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

Label used to indicate issue found during M22 milestone

Label used to indicate issue found during M21 milestone

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 backlog item / Issue / MR affects the community reference implementation

Merge request label for indicating code deprecation, will need to include this in the release notes

Label used to indicate issue found during M20 milestone

Label used to indicate issue found during M19 milestone

Label used to indicate issue found during M18 milestone

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