vigyasharma commented on issue #13797: URL: https://github.com/apache/lucene/issues/13797#issuecomment-2850118949
This is an interesting proposal, and I like the idea of making version upgrades more streamlined. However, I'm a bit confused with how the proposed mechanism should play out. Could you help me understand with an example? Suppose we were to implement this today, we would set `MIN_SUPPORTED_MAJOR = 10` to correspond with Lucene 11. If there are no breaking changes in Lucene 12, 13, and 14 we would not change this value. When we make an index format change, say in Lucene 15.0.0, I assume by your proposal, we would set `MIN_SUPPORTED_MAJOR` to *`14`*, and only ensure backward compatibility logic b/w v14 and v15? Now when Lucene 16.0.0 rolls out, what happens to `MIN_SUPPORTED_MAJOR` version value? If it is kept at 14, then v16 will need to carry forward the backward compatibility logic. Today, by design, we only need to do it for the last release. Is the idea that we'll upgrade `MIN_SUPPORTED_MAJOR` to 15, even if there is nothing breaking b/w 15 and 16? Remembering this logic feels trappy? Or maybe I'm just confused with how this will work. Hopefully you have a better example :) -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
