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)

This issue / MR affects the IBM Implementation on Open Shift

This label is used to indicate direct cherry picks into previous releases for fixing an issue

This issue / MR affects the Google Cloud Platform

This issue / MR captures a change in documentation

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

Component related to DDMS

This issue / MR affects the common code

Merge request label for indicating cherry picks

This issue / MR affects the Azure Cloud Platform

This issue / MR affects the AWS Cloud Platform

Label for issues closed by script or automated processes

Work items related to Airflow2.0

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