rmuir commented on issue #14623: URL: https://github.com/apache/lucene/issues/14623#issuecomment-2859433915
disclaimer: i'm not fully up to speed on the `DocIdSetIterator.intoBitSet` addition that motivated this discussion, but maybe one thought is that it was backported too soon? I'm not trying to suggest that minor releases should become "super-boring" and only have bugfixes, but... when it is an API change to such a central class like DocIdSetIterator with large impact and risk potential, baking in `main` might help. I've had my own frustrations with this approach: pushing scary stuff just to `main`, having it bake for years, and then still not really grab attention until right at release-time, but I think this is something we could improve. It is just a high-level idea, if the goal is to make minor releases more stable, then being selective about what is backported can really help. I still think some things are missing, it isn't a magic bullet to find all bugs if we just "delay" the feature in `main`. Sometimes we get lucky and tests catch stuff, but it is best if people try it out and find the bugs in it. But I think it is more "expected" for end-users to find these kinds of "day 1" bugs in a major release versus in a minor release. It is not cool when they happen in a minor release, so thinking twice about what we backport can help. -- 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
