Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 137
-
DoingOSDU / OSDU Data Platform / Data Flow / Data Ingestion / Energistics DAGs - OSDU Integration / WITSML Parser DAG
-
Energistics IntegrationOSDU / OSDU Data Platform / Data FlowTasks associated with supporting Energistics standards.
-
Energistics IntegrationOSDU / OSDU Data Platform / Data Flow / Data Ingestion / Energistics DAGs - OSDU Integration / WITSML Parser DAG
-
Energistics Internal TaskOSDU / OSDU Data Platform / Data Flow / Data Ingestion / Energistics DAGs - OSDU Integration / WITSML Parser DAG
-
HotfixOSDUThis 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.
-
ImpactMajorOSDU / OSDU Data PlatformUsed on MRs that have breaking changes, therefore requiring a major version bump on the next release.
-
ImpactMinorOSDU / OSDU Data PlatformUsed on MRs that have backwards-compatible new features, therefore requiring a minor version bump on the next release.
-
ImpactPatchOSDU / OSDU Data PlatformUsed on MRs that have bugfixes or optimizations with no changes to features, therefore requiring a patch version bump on the next release.
-
IssueADROSDUAn 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)
-
IssueDefectOSDUA defect is an issue that is a software error, flaw or fault that causes that project or repo or service to produce an incorrect or unexpected result per the OSDU standard or requirements or that it behaves in unintended ways. A defect can be further categorized as a defect in the common code in the PMC project or as a defect within the CSP realization of the PMC project to ensure that it can be targeted towards the right development resource to address this issue.
-
IssueDuplicateOSDUThis label indicates that the issue is a duplicate and there has been a related issue created