Labels

This label signifies that the code is undergoing Final review stage and it will be approved once it is good to go

This label marks the successful merging of the code into the master branch

This label signals that a merge request (MR) has been raised to the master branch

This label indicates that the code is undergoing peer code review and it will be approved once it is good to go

This label indicates that primary testing in the development environment is in progress. The Primary developer is conducting initial testing in the development environment.

This label denotes that secondary testing in the development environment is underway. Secondary developer (or QA) is performing additional testing in the development environment.

This label highlights that unit test cases are being written for the issue

Tasks associated with supporting Energistics standards.

This issue / MR affects the Google Cloud Platform

This 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.

This issue / MR affects the IBM Implementation on Open Shift

Used on MRs that have breaking changes, therefore requiring a major version bump on the next release.

Used on MRs that have backwards-compatible new features, therefore requiring a minor version bump on the next release.

Used on MRs that have bugfixes or optimizations with no changes to features, therefore requiring a patch version bump on the next release.

Data Loading

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)