mjsax commented on PR #18193: URL: https://github.com/apache/kafka/pull/18193#issuecomment-2569954461
Was just catching up on the discussion. Don't think it should be only me, but also @cadonna and @ableegoldman. The main problem I see is, that we don't have any official statement what upgrades we support. So while I agree that is it very unlikely that somebody upgrades from 0.11 to 4.0, our policy so far was that we do support it... Of course, given that 4.0 is a major release, we could start to make a cut. The question is of course where to make the cut. 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...). However, we should make this an official policy, and thus we need to discuss this on the dev mailing list IMHO, but not on a PR... Thoughts? -- 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
