Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🌱 Issue template for preparing new minor release #1748

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+35 −0
Open

🌱 Issue template for preparing new minor release #1748

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions .github/ISSUE_TEMPLATE/prepare_minor_release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
name: Minor release tracking issue
title: Prepare for v<release-tag>
---

Please see this documentation for more details baout release process: https://github.com/metal3-io/metal3-docs/blob/main/processes/releasing.md


**Note**:
* The following is based on the v1.7 minor release. Modify according to the tracked minor release.

## Tasks
* [ ] Uplift CAPI to latest minor in CAPM3, also check migration guide: [Migration guide for providers](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/providers/migrations). [Prior art CAPM3](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1604).
IMPORTANT: Always read migration guide and make sure to do the changes accordingly in CAPM3 and IPAM.
* [x] Uplift k8s to 1.31 in CAPM3 and metal3-dev-env repo. [Prior art metal3-dev-env](https://github.com/metal3-io/metal3-dev-env/pull/1389), [Prior art CAPM3](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1622)
* [x] Uplift k8s to 1.31 in image building pipeline. [Prior art jjb](https://gerrit.nordix.org/c/infra/cicd/+/22205) [Prior art pipeline](https://github.com/metal3-io/project-infra/pull/836)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These 2 uplifts still refer to specific k8s versions, also remove the ticks.

* [ ] Wait for Ironic release. It is tentative depending on when upstream Ironic has bugfix branch available. [Prior art](https://github.com/metal3-io/ironic-image/tags)
* [ ] Wait for BMO release if needed.
* [ ] Wait for IPAM release if needed.
* [ ] Bump IPAM and BMO in CAPM3 [Prior art](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1605)
* [ ] Release CAPM3 (Branch out, add branch protection and required tests, also check new image is created in quay).
* [ ] Prepare dev-env to accommodate new release related changes and configurations [Prior art](https://github.com/metal3-io/metal3-dev-env/pull/1381)
* [ ] Add/edit JJBs to accommodate new build jobs and PR jobs for new release branches. [Prior art](https://gerrit.nordix.org/c/infra/cicd/+/20875)
* [ ] Add Prow jobs for new release branches in Project-infra repo [Prior art](https://github.com/metal3-io/project-infra/pull/697)
* [ ] Check CI if new releases are tested properly or not.
* [ ] Update CAPM3 README.md with the new e2e triggers. [Prior art](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1618)
* [ ] Update Metal3 book. [Prior art](https://github.com/metal3-io/metal3-docs/pull/413)
* [ ] Announce the releases

## Post-release tasks
Do the following on the main branch after the release is done.

* [ ] Add CAPI contract for new minor release. [Prior art](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1937/files)
* [ ] Update clusterctl tests to accommodate new release.
* [ ] Update k8s uplift tests to accommodate new release.