ChrisHegarty commented on issue #14623:
URL: https://github.com/apache/lucene/issues/14623#issuecomment-2866257196

   Thanks @javanna - that captures the dilemma very well, and I really 
appreciate the devil’s advocate angle. Your summary gets to the heart of the 
issue: early adoption is good for Lucene, but it’s high-stakes for downstream 
users without a safe rollback path. That tension is what we’re trying to solve 
- not by expecting Lucene to support multiple formats indefinitely, but by 
introducing just enough flexibility to let early adopters help without risking 
production stability.
   
   You’re right that some bugs will only surface in production, and we’ve seen 
time and again that early rollouts help discover those faster — which benefits 
the entire ecosystem. But for that to be sustainable, we need tools or policies 
that give us room to react. Today, a bad bug means we likely be stuck: we can’t 
downgrade the code because the index format changed, and we can’t write the old 
format because the writer was removed.
   
   This isn't about freezing minor releases - it's about isolating risk so 
adopters can iterate safely and fix forward or roll back with confidence.
   
   I really like the idea of looking at this as a way to encourage faster 
adoption. If users know they can upgrade quickly and safely - with a rollback 
path - I think we’ll see more adoption, not less.
   
   I recognize that my initial proposals might not be the ideal solutions, and 
I'm not strongly advocating for either one in particular. There may be other 
viable alternatives worth exploring — assuming, of course, that supporting this 
kind of scenario is something we agree is worth addressing in Lucene.


-- 
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

Reply via email to