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
10.0.1 release is not synced correct. #1534
Comments
Hrmph, I will take a look. I did have some challenges getting the 10.0.1 done :( |
I am also waiting for that to get fixed or maybe release 10.0.2 ( see #1463 (comment) ) |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale The 10.0.1 release is still not valid. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle rotten What is the most recent release? |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
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. |
@brendandburns I think the same think has happened with the 10.0.1 release that happened with the 9.0.1 release.
To see this take a look at the definition of LeaderElectionConfig in the jar. It doesn't match the source code.
The text was updated successfully, but these errors were encountered: