This document describes how Kruise handles versioning, releases new versions and communicates about them.
Kruise uses semantic versioning so that their users can reliably upgrade according to their needs.
Kruise is using a release schedule of 2 to 3 months and uses GitHub milestones to provide an indication of when the next release is planned. It can, however, happen that releases get delayed which will be reflected on the milestone.
You can learn about our release process here.
We provide a changelog that includes every change per version must be available as part of the repo, for example, here is the changelog for Kruise.
Next to that, every closed issue and PR should be added to a GitHub Milestone that provides an overview of everything that will be included and provide an indication of what the current intended release date is. However, the release date is subject to change and only provides an indication.
Lastly, every new release will come with a GitHub Release which provides the exact changelog for that release.
If you want to be notified of new releases, we recommend watching our openkruise/kruise repository on GitHub and ensure you are subscribing for releases.
Next to that, you can join the conversation for every new release on GitHub Discussions.
- User Documentation
- Community
- GitHub Discussions
- Channel #openkruise in Kubernetes Slack (registration)
- DingTalk：Search GroupID 23330762 (Chinese)