As the month comes to a close our 1.12 release feature freeze is just around the corner (EOD Tuesday July 31).
For anybody unfamiliar with the release process cycle, this is just a feature definition milestone. Code freeze is yet to come, leaving many weeks yet for feature implementation.
The release team and its features lead Stephen Augustus have been checking in with SIGs on feature plans for the release and working to insure the features repo (https://git.k8s.io/features) is up to date. Features not captured and tracked ahead of the feature freeze must go through the exception process (https://git.k8s.io/features/EXCEPTIONS.md).
The current feature list is tracked at http://bit.ly/k8s112-features. If any of your SIG features are missing, please reach out to us ASAP.
SIGs should also be thinking about their release themes (major work focuses) for the 1.12 release notes in addition to insuring those themes are represented in feature issues as described above and have plans for documentation and test coverage. These release themes are a good opportunity for SIGs to communicate with users and contributors on focus areas for the coming weeks, and will feature in an upcoming Blog - Kubernetes posting.
Feature freeze: July 31, 2018
Begin code slush: Aug. 28, 2018
Begin code freeze: Sept. 4, 2018
End code freeze: Sept. 19, 2018
Release date: Sept. 25, 2018
Detailed information available at http://bit.ly/k8s112-release-info
Tim Pepper, 1.12 release lead