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.

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

Have release artifacts available for BMO #2089

Closed
tuminoid opened this issue Nov 28, 2024 · 6 comments
Closed

Have release artifacts available for BMO #2089

tuminoid opened this issue Nov 28, 2024 · 6 comments
Labels
needs-triage Indicates an issue lacks a `triage/foo` label and requires one.

Comments

@tuminoid
Copy link
Member

We currently don't have any release artifacts for BMO. Following CAPM3 and IPAM, we should have some manifests available, where we can set the tags etc. Committing them to repo like this suggestion is not right. Checking k8s, CAPI, CAPM3 etc the template is unchanged, but release artifacts are corrected.

We should decide what are the release artifacts for BMO, and add them to the releasing automation.

@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Nov 28, 2024
@metal3-io-bot
Copy link
Contributor

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@tuminoid
Copy link
Member Author

@kashifest @adilGhaffarDev as discussed offline.

@tuminoid
Copy link
Member Author

tuminoid commented Dec 2, 2024

#1722 more or less a duplicate. Which one to close discussed there.

@Rozzii
Copy link
Member

Rozzii commented Dec 2, 2024

On principle I would close the new and just add your issue description as a comment to the old one.

@tuminoid
Copy link
Member Author

tuminoid commented Dec 2, 2024

/close
OK, let's continue on the older issue, refine it there.

@metal3-io-bot
Copy link
Contributor

@tuminoid: Closing this issue.

In response to this:

/close
OK, let's continue on the older issue, refine it there.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants