-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Discuss cutting kube-state-metrics v1.6.0 #697
Comments
Sounds good to me 👍 |
Whoops typo I meant #650 |
Sure, I understand. Also, if it doesn't have any activity, I don't mind picking one of them up. We can also open it up to potential contributors in the Kubernetes slack. Thoughts? |
Or if we want to cut the 1.6.0 release sooner, we can just wait until the next minor release too. |
Pinging people on kubernetes slack as a first measure sounds like a good idea. As we don’t have a regular release cadence, I think it’s ok to also cut the next minor release closer to this one if needed. |
Let's cut this! |
Agreed. @mxinden you want to take care of this? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
v1.6.0 has already been released. |
Given that the last release was cut ~2 month ago and master being ahead of release-1.5 by 107 commits, what do you all think of cutting a v1.6.0 release?
The text was updated successfully, but these errors were encountered: