markrmiller commented on issue #13797: URL: https://github.com/apache/lucene/issues/13797#issuecomment-3182499370
> Other than putting an extra effort on the shoulders of the release manager Ideally, if anything, it would be a slightly smaller burden as they would no longer increment the min supported version. It would be incremented when a change goes in that requires it. Given the rarity and nature of such a change, its doubtful that it would be very commmon to miss I think, unlike more common breaks sometimes missing their way into MIGRATE.md for example. Unless the change was like, snuck in, and nobody knew about it. But even if a break went in and it was missed, it wouldn't really be a very big deal. There is no promise you get this kind of upgrade, it would be noted when it became apparent, and I'm still supportive of the idea of documenting this path as taking on some possible danger vs the current options. Reindexing is always best of you can manage it. -- 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
