Skip to main content

Introduction

info

Starting in August 2025, we dropped the Git Flow based process in favor of having parallel maintenance version branches.

TL;DR

For the following we use two scenarios:

  • Release approval for major version 2506.0 (starting from main).
  • Release approval for minor version 2406.1 (starting from maintenance/2406.x).

This section will guide you through a typical development, approval and release process. We will guide you in parallel through the approve and release process for a CMCC major version, as well as for a CMCC minor version.

NOTE: Powered by Mermaid

Each step will be guided by Git Graphs (powered by Mermaid).

For the following description, we expect the following starting points regarding the Git and documentation perspective.

Thus, we have approved the GCC integration for (major) versions CMCC v12.2406.0.0 and CMCC v12.2412.0.0.

INFO: Deploy Documentation from Main

Only documentation updates on origin/main branch will eventually be deployed to gh-pages, thus, published. For subsequent maintenance releases, the corresponding documentation is only updated within the repository sources.

WARNING: Stick to CMCC Release Order

Approvals done on a given branch like origin/main should be performed in the same order as releases in the CMS. Thus, if you happen to have a delay in your approval process, and 2412.0.0 as well as 2506.0.0 need to be approved, you should stick to first approving 2412.0.0.

If you deviate from this, you must ensure to skip merging a created maintenance/2412.x branch to origin/main.