jtibshirani commented on pull request #588: URL: https://github.com/apache/lucene/pull/588#issuecomment-1010270045
@zacharymorn here's my understanding of our usual strategy: on every branch of the same major release, the change always appears under the same release (like `9.1.0`), corresponding to the earliest release that contains the change. In addition, I'm not sure we preemptively backport changes unless we think they'll be released. For example, it's not clear we'll have a 9.0.1 or 8.11.2 release. If we did decide to have one, we could backport the change at that point and move the changelog entries. (But I do see some existing changelog entries for 9.0.1, hmm, maybe others are planning something). Maybe we can keep it simple with this change and just backport to `branch_9x`, and the changelog entry would be `9.1.0` everywhere? -- 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
