🌱 Issue template for preparing new minor release #1748
+25
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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 |
metal3-io-bot
added
the
approved
tuminoid
reviewed
Jun 10, 2024
|
|
||
| * [ ] 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.
I think we should not put past release versions in the template.
There was a problem hiding this comment.
removed versions, can you check again
metal3-io-bot
added
the
do-not-merge/hold
Signed-off-by: adil ghaffar <muhammad.adil.ghaffar@est.tech>
adilGhaffarDev
force-pushed
the
add-prepare-minor-temp/adil
branch
from
d8e415b
to
b455689
Compare
metal3-io-bot
added
the
size/S
tuminoid
reviewed
Jun 25, 2024
| * [ ] 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.
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.
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.
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.
Suggested change
| * [ ] 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) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.