Discuss cutting kube-state-metrics v1.6.0

[mxinden]

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?

[brancz]

Sounds good to me 👍

[tariq1890]

Possible to fit PRs #610 and #654 into the release?

[brancz]

#654 is already merged, so yes, #610 I'm not so sure about as it will need some follow up and I'd be ok if it lands in the next release

[tariq1890]

Whoops typo I meant #650

[tariq1890]

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?

[tariq1890]

Or if we want to cut the 1.6.0 release sooner, we can just wait until the next minor release too.

[brancz]

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.

[tariq1890]

Let's cut this!

[brancz]

Agreed. @mxinden you want to take care of this?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[brancz]

v1.6.0 has already been released.