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

Bump CAPI to v1.5.0 #4390

Closed
richardcase opened this issue Jul 10, 2023 · 5 comments · Fixed by #4510
Closed

Bump CAPI to v1.5.0 #4390

richardcase opened this issue Jul 10, 2023 · 5 comments · Fixed by #4510
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@richardcase
Copy link
Member

/kind feature
/help

Describe the solution you'd like
We want to bump CAPI to 1.5.0 (as soon as its released).

Anything else you would like to add:
We have an issue to bump to the RC: #4375

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot
Copy link
Contributor

@richardcase:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/kind feature
/help

Describe the solution you'd like
We want to bump CAPI to 1.5.0 (as soon as its released).

Anything else you would like to add:
We have an issue to bump to the RC: #4375

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 10, 2023
@richardcase
Copy link
Member Author

/triage accepted
/priority important-soon
/milestone v2.3.0

@k8s-ci-robot k8s-ci-robot added this to the v2.3.0 milestone Jul 10, 2023
@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jul 10, 2023
@furkatgofurov7
Copy link
Member

/assign

@richardcase
Copy link
Member Author

@furkatgofurov7 - just to confirm this is for the 1.5.0 release and not the rc

@furkatgofurov7
Copy link
Member

@furkatgofurov7 - just to confirm this is for the 1.5.0 release and not the rc

@richardcase sure, I can bump it to actual release once it is out too, for now opened #4398 to bump it to rc.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants