[RELEASE] Release v1.8.0

[github-actions]

What's the task? Please describe

Action items for releasing v1.8.0

Roles

• Release captain: @derekbit
• QA captain: @derekbit

Describe the sub-tasks

Pre-Release

Release Captain Tasks

Important

The Release Captain needs to finish the following items

• This tasks are only needed when doing a feature release such as v1.8.0.

  • Before creating RC1, create a new release branch for the following component repositories by trigger the ▶️ Create Longhorn Repository Branches Action, and then create RC1 from the new branch. Leave the master branch for the next feature release development.
  • Add the new branch to renovate configuration.
    • PR:
  • After creating the new release branch, update the version file in each repo by ▶️ Update Longhorn Repository Version File in Default Branch Action.
    • longhorn-manager
    • longhorn-ui
    • longhorn-tests
    • longhorn-engine
    • longhorn-instance-manager
    • longhorn-share-manager
    • backing-image-manager
    • longhorn-spdk-engine (needed after GA)
    • cli
  • Update jobs.release.strategy.matrix in sprint release.
    • PR:
  • Create sub-issue Regular Tasks for Feature Release ticket in longhorn/longhorn.
    • PR:

• This tasks are only needed when doing a patch release

  • Create sub-issue Regular Tasks for Patch Release ticket in longhorn/longhorn.
    • PR:

• Create sub-issue Fix CVE issues for v1.8.0 ticket in longhorn/longhorn -

  • PR:

• Trigger the RC release build by ▶️ Release-Preview Action.

QA Captain Tasks

Important

The QA captain needs to coordinate the following items before the GA release.

• Regression test plan (manual)

• Update Longhorn official document

  • Update Best Practices>Operating System and Best Practices>Kubernetes>Kubernetes Version
    • PR:

• Run e2e regression for pre-GA milestones (install, upgrade)

• Run security testing of container images for pre-GA milestones.

  • Investigate and fix the security issues. The issues are tracked by the sub-issue Fix CVE issues for v1.8.0 -
  • Create security issues at upstream for unresolved CVEs in CSI sidecar images -

---

Release

Release Captain Tasks for the GA Build

Important

The Release Captain needs to finish the following items

• This tasks are only needed when doing a feature release such as v1.8.0.
  • Ensure the sub-issue Regular Tasks for Feature Release for v1.8.0 is completed.
  • Ensure the sub-issue Fix CVE issues for v1.8.0 is completed.
• Update image versions in chart/README.md.
  • PR:
• Update image versions in chart/questions.yaml.
  • PR:
• Trigger the GA release build by ▶️ Release Action.

QA Captain Tasks for the GA Build

Important

The QA captain needs to coordinate the following items before the GA release.

• Run security testing of container images for GA build
• Verify longhorn chart PR to ensure all artifacts are ready for GA build (install, upgrade)
• Run core testing (install, upgrade) for the GA build
  • Upgrade from the previous patch of the same feature release.
  • Upgrade from the last patch of the previous feature release.

Release Captain Tasks after Completing the GA Build Validation

• Create a release note (CHANGELOG).

  • Deprecation note.
    • PR:
  • Update notes including highlighted notes, deprecation, compatible changes, and others impacting the current users.
    • PR:

• Update Longhorn official documentation.

  • Update config.toml and publish the new version of doc and add a next patch version of dev doc.
  • Update image versions in References > Helm Values and Snapshot and Backups > CSI Snapshot Support > Enable CSI Snapshot Support on a Cluster.
    • PR:
  • Update Important Notes.
    • PR:

• Publish the GA release in longhorn/longhorn and longhorn/cli.

• Release longhorn/chart from the release branch to publish to ArtifactHub by ▶️ Release Charts on Demand Action.

• Mark the release as latest release in longhorn/longhorn README.md.

  • PR:

• Update jobs.release.strategy.matrix in sprint release.

---

Post-Release

• Mark the release as stable release and update stable versions in https://github.com/longhorn/longhorn/blob/master/support-versions.txt
  • For the first stable release, we need to consider several factors and reach a consensus by maintainers before claiming it stable.
  • For any patch release after a stable release, we need to wait 1-2 weeks for user feedback.
  • PR:

After marking the release as a stable release, Release Captain needs to coordinate the following items

• Update https://github.com/longhorn/longhorn/blob/master/deploy/upgrade_responder_server/chart-values.yaml -
  • PR:
• Add another request for the rancher charts for the next patch release -
• Update the support matrix -

Rancher Charts

The Release Captain needs to coordinate the following items.

• Verify the chart can be installed & upgraded - @derekbit
• rancher/image-mirrors update -
• rancher/charts active branches for Rancher App Marketplace -