As Kubernetes nears its 1.0 release, it’s time to deliberately slow the pace of commits and drive towards a stable release. We have added many features and fixes recently, and have only a few remaining in the 1.0 milestone.
We’re going to implement a code freeze at the end of this week (Friday May 22). PRs submitted past that point will end up in one of two states:
If it’s work required for a 1.0 feature, or a bug that needs to be fixed for 1.0, we’ll review and merge as usual
If it’s not required for 1.0, we will place the PR in the v1.0-post milestone and return to it once 1.0 ships
Reducing the churn and focusing on testing, usability, reliability, performance and documentation will be critical to landing a successful 1.0 release.
Thank you for all your involvement so far in bringing Kubernetes to this point. We’re on the verge of something great.