Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
This Issue / MR affects the security aspects of the Data Platform
-
Merge request label for indicating new feature change, generally requires accompanying ADR
-
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
-
A feature request is an issue that is either a new requirement that needs software changes, new feature development (perhaps requiring new repos, sub-projects or new PMC projects). This request needs to follow an ADR that provides enough clarity on the requirement, the definition of done, impact of changes and other necessary attributes so the issue can be curated and moved up in life cycle. May require an entry in Aha portal.
-
Merge request label for indicating code deprecation, will need to include this in the release notes
-
These are the activities that have been prioritized to start next
-
Issue life cycle label: These are activities that have been placed on hold, either because of a blocking factor or displaced by a higher priority
-
Issue regarding work related to code clean ups/refactoring/optimization
-
Merge request label for indicating fix for defect, software error, unintended behavior, flaw or fault within the code
-
Merge request label for indicating initial development of a project
-
Merge request label for indicating work related to code clean ups/refactoring/optimization
-
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.
Prioritized