-
Notifications
You must be signed in to change notification settings - Fork 87
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.
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 #1748
base: main
Are you sure you want to change the base?
Conversation
That is the great addition. Thanks @adilGhaffarDev |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
|
||
* [ ] Add/edit JJBs to acommodate 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) | ||
* [ ] Prepare dev-env to acommodate release-1.7 related changes and configurations [Prior art](https://github.com/metal3-io/metal3-dev-env/pull/1381) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should not put past release versions in the template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed versions, can you check again
Signed-off-by: adil ghaffar <muhammad.adil.ghaffar@est.tech>
d8e415b
to
b455689
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NItting, but also questioning should this be somewhere else than CAPM3?
* [ ] Add Prow jobs for new release branches in Project-infra repo [Prior art](https://github.com/metal3-io/project-infra/pull/697) | ||
* [ ] Prepare dev-env to acommodate new release related changes and configurations [Prior art](https://github.com/metal3-io/metal3-dev-env/pull/1381) | ||
* [ ] Update Metal3 book. [Prior art](https://github.com/metal3-io/metal3-docs/pull/413) | ||
* [ ] Release Ironic, also check new image is created in quay. [Prior art](https://github.com/metal3-io/ironic-image/tags) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ironic-image release process is not part of CAPM3 minor release process. It is released separately when upstream Ironic has bugfix branch available. Maybe mark it as optional ?
* [ ] Prepare dev-env to acommodate new release related changes and configurations [Prior art](https://github.com/metal3-io/metal3-dev-env/pull/1381) | ||
* [ ] Update Metal3 book. [Prior art](https://github.com/metal3-io/metal3-docs/pull/413) | ||
* [ ] Release Ironic, also check new image is created in quay. [Prior art](https://github.com/metal3-io/ironic-image/tags) | ||
* [ ] Pin Ironic in BMO and release BMO, also check new image is created in quay. [Prior art](https://github.com/metal3-io/baremetal-operator/pull/1679) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IPAM mentions branching out etc, how is BMO any different?
* [ ] Update Metal3 book. [Prior art](https://github.com/metal3-io/metal3-docs/pull/413) | ||
* [ ] Release Ironic, also check new image is created in quay. [Prior art](https://github.com/metal3-io/ironic-image/tags) | ||
* [ ] Pin Ironic in BMO and release BMO, also check new image is created in quay. [Prior art](https://github.com/metal3-io/baremetal-operator/pull/1679) | ||
* [ ] Release IPAM (Branch out, add branch protection and required tests, also check new image is created in quay). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why were documenting IPAM/BMO/Ironic releasing in CAPM3 repo, shouldn't we have this tracking issue in more generic repo, like docs or dev-env or community? Most of these steps do not related to CAPM3 after all.
* [ ] 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). | ||
* [ ] Check CI if new releases are tested properly or not | ||
* [ ] Update CAPM3,IPAM and BMO README with the new e2e triggers. [Prior art][CAPM3](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1618), [IPAM](https://github.com/metal3-io/ip-address-manager/pull/504),[BMO](https://github.com/metal3-io/baremetal-operator/pull/1694) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* [ ] Update CAPM3,IPAM and BMO README with the new e2e triggers. [Prior art][CAPM3](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1618), [IPAM](https://github.com/metal3-io/ip-address-manager/pull/504),[BMO](https://github.com/metal3-io/baremetal-operator/pull/1694) | |
* [ ] Update CAPM3, IPAM and BMO README.md with the new e2e triggers. [Prior art][CAPM3](https://github.com/metal3-io/cluster-api-provider-metal3/pull/1618), [IPAM](https://github.com/metal3-io/ip-address-manager/pull/504),[BMO](https://github.com/metal3-io/baremetal-operator/pull/1694) |
What this PR does / why we need it:
This PR is adding an issue template for preparing a new minor release. It will make it easier to create tracking issue.