## **Mixed Dependency Strategy for building and releasing.**

This strategy is designed to resolve the inherent conflict between the continuous development churn of upstream repositories (e.g., devel:languages:python, or DLP) and stability of our products.

The primary goal is to ensure **consistency, reproducibility, and stability** across all releases by creating a stabilized build environment.

1. **RPM First:** All components, including dependencies, are built and managed as stable RPM packages.
2. **Stabilization Firewall:** Mission-critical dependencies are consumed from controlled **Private Copy** projects (Deps:\*) to prevent unexpected breakage from upstream changes in DLP.
3. **Parallel Versions:** The main RPM and final container artifact support parallel releases via a structured versioning scheme. i.e `mcp-server-uyuni.x.y.z`
4. **Container Release:** The primary deliverable is a versioned container image. **This is the sole artifact for distribution.**. Thus, the rest of packages are **build dependencies**.

## **Dependency Subprojects**

The following Open Build Service (OBS) projects contain the full **copied source files and spec files** of required dependencies:

* Deps:devel:languages:python
* Deps:devel:languages:python:backports
* Deps:science:machinelearning:mcp

To add more packages, use ```copypac -e``` for existing packages into the Deps subprojects. For new packages, package them in this project.

## **Release Destination and Immutability**

The final container artifact is released into the **Stable Subproject**. This project is designated for release versions that must never change:

* Multiple versions of the container image can coexist in the Stable Subproject.
* **Containers in the Stable Subproject must never be rebuilt.** This guarantees the integrity of the published artifact.

To create a new release, use ```osc release``` .

## **Legal Disclaimer and Status (Tech Preview)**

All artifacts are provided strictly for **prototyping, development, and feedback gathering**. They are considered a **Technology Preview**.

**The artifacts are explicitly NOT supported or maintained, and there is NO WARRANTY, expressed or implied, of any kind.**

Usage Restriction:
These artifacts must not be deployed or used in any production environment, in mission-critical systems, or where any failure, disruption, or error could result in damages or loss. Users accept all associated risks by deploying this Tech Preview software.