Merge request label for indicating fix for security

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

Issue related to documentation

Merge request label for indicating initial development of a project

Merge request related to an enhancement or upgrade of the existing code, increasing the efficiency or effectiveness of the software without necessarily introducing new features to end user.

Merge request label for indicating work related to internal audit, logging, reporting improvement

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.

Merge request label for indicating reverting change

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.