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

🌱 Issue template for preparing new minor release #686

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

🌱 Issue template for preparing new minor release #686

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
18 changes: 18 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,18 @@
---
name: Minor release tracking issue
title: Prepare for v<release-tag>
---

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

Choose a reason for hiding this comment

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

Don't use bare links. Also wrap 80.



**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 IPAM, 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 ](https://github.com/metal3-io/ip-address-manager/pull/497).
Copy link
Member

Choose a reason for hiding this comment

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

Can we wrap this at 80

IMPORTANT: Always read migration guide and make sure to do the changes accordingly in CAPM3 and IPAM.
* [ ] Verify all go modules are matching with hack/verify-release.sh script.
Copy link
Member

Choose a reason for hiding this comment

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

Not just go modules, but all issues reported by it.

* [ ] Release IPAM (Branch out, add branch protection and required tests, also check new image is created in quay).
Copy link
Member

Choose a reason for hiding this comment

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

We have documentation for this, so rather than listing just some items, maybe link the doc instead, or list all the things needed to do. Promote use of verify-release.sh for post release checks too.

Copy link
Member

Choose a reason for hiding this comment

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

As this is issue template, I would lean towards listing all the things that needs to be done. It will give clear view of release process.

* [ ] Update IPAM README.md with the new e2e triggers. [Prior art](https://github.com/metal3-io/ip-address-manager/pull/504).
* [ ] Announce the releases