This issue / MR affects the common code

Any issues that need discovery / evaluation to get team to starting point, will be part of this title

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)

"no-detached-pipeline" label for the committer pipeline

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

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)

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

This is an item that is carried over from the R2 implementation to R3.

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 life cycle label: This is where the work is happening