-
Notifications
You must be signed in to change notification settings - Fork 336
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
v3.1.1 CHANGELOG #747
v3.1.1 CHANGELOG #747
Conversation
## Changes by Kind | ||
|
||
### Bug or Regression | ||
- Storage capacity: managed-by label potentially too long with a long node name and enableNodeDeployment set to true ([#739](https://github.com/kubernetes-csi/external-provisioner/pull/739), [@akalenyu](https://github.com/akalenyu)) |
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.
so this is the only critical bug we want to fix in a patch release? Just want to understand how we pick which one to include or not.
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.
A user asked for it. There is no systematic triaging of bugs and no automatic backporting of bugs.
From https://kubernetes-csi.github.io/docs/project-policies.html (emphasis mine):
Every minor release branch will be supported with patch releases on an as-needed basis for at least 1 year
@pohly are we planning |
There's going to be a 3.2.0 from the code in master.
Yes. |
/lgtm |
/assign @jsafrane For approval. |
/hold cancel Additional backport PRs were merged, changelog was updated. @jingxu97 : please re-add LGTM |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jingxu97, jsafrane, pohly 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 |
@jsafrane: can you also LGTM? |
/lgtm |
PR #747 was merged without refreshing it first.
What type of PR is this?
/kind documentation
Does this PR introduce a user-facing change?: