Missleading version 3.0.x for supporting older kafka versions

[leisma]

There are new 3.0.x releases that support older Kafka versions, while the newer 2.5.x releases move forward and support the latest Kafka versions. It’s a bit misleading that the higher version (3.0.x) number corresponds to the releases for older Kafka versions. Would it make sense to bump the Cruise Control version that supports the current Kafka versions to 4.0, so that its version number (now 4.0.x) is higher than the one (3.0.x) targeting the older Kafka versions?

[kyguy]

Hi @leisma, you are right, the current versioning scheme for upstream Cruise Control releases is not very intuitive.

Right now, the Cruise Control project is maintained on the following branches and versioned the following way:

• main

  • Supports Kafka versions [3.8.0, 4.0.0]
  • Cruise Control versioning == 2.5.x

• migrate_to_kafka_3_0

  • Supports Kafka versions [3.0.0, 3.8.0)
  • Cruise Control versioning == 3.0.x

Since the main branch is where the latest development is taking place it would be more intuitive if the versions released from this branch had a higher semantic version than versions released from other branches.

Would it make sense to bump the Cruise Control version that supports the current Kafka versions to 4.0, so that its version number (now 4.0.x) is higher than the one (3.0.x) targeting the older Kafka versions?

Yes, I agree, it would make the Cruise Control versioning more intuitive if the major.minor versions of Cruise Control releases matched the the current Kafka version that the Cruise Control release supports. For example, the next release of the main branch which supports Kafka v4.0.0 would be 4.0.x. We should open a GitHub issue for this, I'll open one for it next week if you don't and then we can drive/discuss this solution with the maintainers together!

[leisma]

Hi @kyguy, thanks for your detailed answer! I opened an issue (#2323) for it so we can discuss this solution with the maintainers.