...
What About Version Numbers?
Feature releases will be a minor release by default 0.10.1, 0.10.2 - unless:
- We break compatibility (i.e. remove deprecated public methods after a reasonable period), in which case we bump to 0.11.x
- We change the message format, in which case we bump to 0.11.x
- We do something totally amazing (exactly once?) and decide to bump to 1.X to celebrate *
* We will bump that major release version for Oct 2017 to 1.0.0, with a slight difference in terms of the version numbers such thatSince the 1.0.0 release in Oct 2017, our current versioning protocol is the following:
- We will use three digits instead of four for the release versions:version: major.minor.bug-fix. The first digit would indicate the major revision (starting at 1), and second indicating minor revision, and the last one number indicating the bug-fix revision; when .
- When preparing RCs of the release we will still suffix it after the release version number. I.e. major.minor.bug-
...
- fix [
...
- rc_number]
Feature releases will be a minor release by default (i.e. we will only bump up the minor revision digit) unless:
- We change the message format in Kafka.
- We break compatibility (i.e. remove deprecated public methods after a reasonable period).
- We make major version changes on our dependent projects or when we drop an old Java / Scala support version.
- We do something totally amazing (exactly once?) and decide to release as a new major version milestone.
In those cases, we will bump the major revision digit.
Schedule
The proposed schedule for Apache Kafka is shown below. We will do a release in October and align the releases from January in 2017. We will follow a 4 month schedule for Apache Kafka releases.
...