Home

There is a CODEOWNERs file defining teams responsible by each chart:

https://github.com/rancher/charts/blob/release-v2.9/.github/CODEOWNERS

Current latest active release branch: release-v2.9

Branches

• dev-2.X branches contain charts that are under active development, to be released in an upcoming Rancher release.
• release-v2.X branches contain charts that have already been developed, tested, and released on an existing Rancher release.

Issues

All issues related to this repository must be created in the rancher/rancher repository.

Releases

The release team currently handles the release process.

Every month, we have the Rancher release cycle and, with it, the charts cycle.

Any chart owner can request an Out of Band Release (i.e., a chart release for a single chart out of the rancher release cycle).

Batch Charts Release with Rancher Release process

1. The dates with the detailed process are communicated at team-rancher-release-coordination.
2. The chart owners merge their respective charts on the dev-v2.* branch.
3. The chart owners communicate to the Release Team once the chart is ready.
4. The release team will open the respective PRs to release the charts.

Out-of-Band Release process

1. The chart owners will request an Out-of-Band release scheduled at team-rancher-release-coordination.
2. The chart owners will provide the QA sign-off and have the charts merged at the dev-v2.* branch at the agreed date.
3. The release team will open the respective PRs to release the charts.

Workflow

Generally speaking, this is the default workflow on the repository:

flowchart LR;
  subgraph BigBox[Workflow]
    direction TB
    subgraph A[Chart owners]
        direction LR
        A1[Develop on dev-v2.* branch] --- A2[Raise PR; owners review && merge] ---  A3[Ask for a QA sign-off]
    end
    subgraph B[Release Team]
        direction LR
        B1[Open a Release PR from dev to release branch] --- B2[Validations] --- B3[Communication to the company]
    end
    A --> B
  end

Loading