chia7712 commented on PR #18193: URL: https://github.com/apache/kafka/pull/18193#issuecomment-2570125768
> In the past, ie, 0.x and 1.x release cycles, we did push out major versions more frequently, and it was reasonable to have a longer window with regard to major versions. With 2.x and 3.x however, we did 9 and 10 releases (ie, 3 years!) each, so it might be sufficient to only support a single major version... Ie, we would only support upgrading from 3.x to 4.x (what is still 3 years worth of releases...), but even drop 2.8.x and older. Not sure if we want to make such a hard cut right away (or still include 2.x for now), but overall it would make sense to me (and we might want to do this at least with 5.x release...). Following the KIP-896 baseline provides a straightforward approach to defining the upgrade path. For example, for clients and streams: [0.7 - 2.0] -> [2.1 - 3.9] -> 4.0+ Given that the release date of 2.1.0 was "Released Nov 20, 2018," this approach offers a substantial window for client upgrades. I suggest including upgrade support for 2.x clients/streams in the 4.0 release and then moving the baseline to 3.x in the 5.0 release. -- 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
