mikemccand commented on PR #14977: URL: https://github.com/apache/lucene/pull/14977#issuecomment-5166618723
It looks like we forgot to backport this PR to 10.x back when we did it originally ~11 months ago? Leading to [this regression released in 10.5.0](https://github.com/apache/lucene/issues/16419) where `.vec` open file handles are left hinted for sequential IO (carryover from merging), not the `RANDOM` that Lucene had intended to hint. I find we (including me!) are not great at backporting :) In general, our policy is to backport (`main` -> `branch_10x` now) everything, and only make exceptions for specific reasons like new features in java/panama that cannot work on older JVMs allowed by `branch_10x`. This then means that our dev efforts get to users faster, we get feedback faster, iterate faster, etc. Stuff trapped on `main` doesn't really get used until we do a next major release (and I think @uschindler is itching to get 11.0.0 out!). I wish we had stronger mechanisms (dev/GitHub tooling), instead of relying on we humans to remember to do things, like some kind of bot that runs when we merge a PR to `main` and assesses if we should backport and at least nags us and/or maybe opens a cherry-pick PR. I think I've seen discussions already along these lines? Long ago, feels like an eternity in AI-days but is probably like 2 weeks really, I tried to CC (Claude code) a solution and it seemed compelling but I never finished it. Anyone have some simple baby steps creative ideas? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
