zacharymorn edited a comment on pull request #588: URL: https://github.com/apache/lucene/pull/588#issuecomment-1010702372
Thanks @jtibshirani for the suggestions here! I have a few follow-up questions: > @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. > > 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? I think my main reasoning here is that since this change is a bug fix, it should ideally go to `branch_9_0` first for the next / first bug patch release for version 9. In addition, since branch `branch_9x` was already cut for `9.1.x` and onward, this fix should be backported to `branch_9x` as well so that future non-9.0.x versions also have it . Maybe the best strategy here would be to keep the change entry for whichever version that goes out first (I think it will be `9.0.1`? ), and for the other one we can skip the change entry to avoid duplication? > 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). I would actually imagine `9.0.1` release to happen soon (and before `9.1.0`?) given it is the first bug fix release for version 9. I'm fine with holding off backporting to `8.11.2` if there's no plan for it soon, but not sure what will be the best mechanism to track this delayed backport if `8.11.2` were to be released later on? Shall I mark this as a blocker for `8.11.2` in Jira? -- 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
