|

|
|

|
|
|
|
|
|
# ELT Platform Lifecycle
|
|
# ELT Platform Lifecycle
|
|
|
|
|
|
## Streams
|
|
## Streams
|
|
|
|
|
|
* **ELT Platform Next** - ELT Packages Collection aimed at the next major release. Bleeding edge development stream for ELT DevEnv and ECOS packages.
|
|
* **ELT Platform Next** - The ELT Packages Collection is aimed at the next major release. It is a bleeding-edge development stream for ELT DevEnv and ECOS packages.
|
|
* Builds against multiple targets (Base OS)
|
|
* Builds against multiple targets (Base OS).
|
|
* No restrictions on update policy
|
|
* No restrictions on update policy.
|
|
* Broken packages are allowed
|
|
* Broken packages are allowed.
|
|
* With current infrastructure state no CI pipelines for that stream
|
|
* No CI for that stream (with current infra state).
|
|
* **Yearly Branches** - ELT Packages Collection aimed at the yearly public and biannual CCS releases. Yerly Branches are branch out from ELT Plaform Next. Quite stable development stream for higher level ELT Control Software Projects like IFW, RTCTK, HLCC, LSVs, and TREx.
|
|
* **Yearly Branches** - The ELT Packages Collection is aimed at the yearly public and biannual CCS releases. Yearly Branches are branched out from ELT Platform Next. Quite stable development stream for higher level ELT Control Software Projects like IFW, RTCTK, HLCC, LSVs, and TREx.
|
|
* Build and tested against one target (Base OS)
|
|
* Build and tested against one target (Base OS).
|
|
* Relaxed update policy
|
|
* Relaxed update policy.
|
|
* Broken packages should be fixed fast
|
|
* Broken packages should be fixed fast.
|
|
* Stream fully supported by CI
|
|
* Stream fully supported by CI.
|
|
* **Release Branches**
|
|
* **Release Branches** - The ELT Package Collection branched out from Yearly Branch or another Release Branch. The Release Branch is used to stabilize the release and deliver eventual patches and bug fixes.
|
|
|
|
* The ELT DevEnv team provides infrastructure and support for two release branches yearly.
|
|
|
|
* Public release, and CCS release - owned by IFW, RTCTK, HLCC, and CCS.
|
|
|
|
* CCS release - owned by CCS.
|
|
|
|
* The ELT DevEnv team may provide support and infrastructure for more release branches for a cost of 0.2 FTE covered by the requesting party.
|
|
|
|
* Strict update policy. Owners of a branch have exclusive rights to decide about updates.
|
|
|
|
* Broken packages are not allowed,
|
|
|
|
* Stream fully supported by CI.
|
|
|
|
|
|
## Versioning
|
|
## Versioning
|
|
|
|
|
... | | ... | |