-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Changelog for 2.6.0 #300
Changelog for 2.6.0 #300
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mauriciopoppe The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
456efa3
to
44aa477
Compare
44aa477
to
f19b84f
Compare
@mauriciopoppe shall we publish a release for 2.5.0 now? current latest release is v2.4.0, so it should be v2.5.0 release. Let me know what I could help, thanks. |
yes, I think somewhere in the dev process I made a mistake and pushed the helm chart with v2.5.0, anyways I think we could match the helm version with the repo version and have v2.6.0 for the next release |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
I'll create a new one instead. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
CHANGELOG for 2.6.0, generated with the instructions in RELEASE.md from #299
Release note:
/hold
Waiting for other changes to be merged, I'll keep the new file up to date #299