Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
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.
-
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 version upgrade of libs
-
This issue relates to improving or introducing unit testing, integration, or automation in code testing
-
The ADR has been raised in the community and respective contributor members have been notified to provide feedback and reviews.
-
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.
-
An implemented solution that has been marked as retired/obsolete
-
A decision that has been rejected for various technical and business reasons
-
A proposed solution for an issue that requires deliberation and changing of existing behavior
-
A decision that has been approved for an ADR, issue needs to be accompanied by Progress label KB::In Progress, KB::Done
-
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)
Prioritized