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.

Label used to indicate issue found during M18 milestone

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

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

Issue related to documentation

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.

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

Merge request label for indicating CICD related / DevOps changes for release management

Merge request label for indicating reverting change

A decision record (DR) is a result of an process inefficiency where a new OSDU practice that has agreed to address the existing process inefficiency (perhaps requiring new process, operation patterns)

This label indicates that the issue is a duplicate and there has been a related issue created

This issue requires further information but lack of responses from submitter. Close after inactivity for more than 6 months.

This issue has been reviewed and confirmed that it is not an issue but rather an intended behavior/operational issue/basic query.