chia7712 commented on PR #18193: URL: https://github.com/apache/kafka/pull/18193#issuecomment-2571564107
> I don't really think that KIP-896 is in the center, as it defines broker-client cross-version compatibility, while we are discussing KS upgrade compatibility... I totally agree that it is a different issue. However, it would be beneficial to have a consistent matrix. Otherwise, users might upgrade their client to a "recommended" bridge version only to find that it lacks support for necessary protocols... > [0.11.x - 1.x] -> [2.0 - 3.9] -> 4.x I want to emphasize that version 4.x occupies the central position, and therefore, either an upgrade path or protocol compatibility is crucial for mitigating the anxiety associated with adopting 4.x. Consequently, including version 2.0 in the bridge version could potentially result in compatibility issues with the 4.0 broker. This effectively renders the bridge unusable, as users would be unable to even conduct basic testing. > It's confusing why 2.0 would be in the first bucket, but not in the second one... This makes sense to me. I haven't investigated this thoroughly, but perhaps another approach would be to include version 2.0 within the scope of protocol changes. This would enable us to suggest a consistent upgrade/testing path for users: [0.11.x - 1.x] -> [2.0 - 3.9] -> 4.x -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
