jtibshirani commented on pull request #588: URL: https://github.com/apache/lucene/pull/588#issuecomment-1012582171
> 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? Yep, this seems like the right strategy. There should only be one changelog entry, and it should be the same version in both `main` and `branch_9x`. > 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 not sure that we'll release 9.0.1, I haven't seen any email message proposing it. From my understanding, we don't always make patch releases if there are bug fixes, often we just jump to the next minor. I think that most developers just backport to the unstable branches `main` and `branch_9x`. Then someone sends an email proposing "I'd like a bugfix release 8.11.2, is there anything you want to add before I cut the branch?" Then people backport fixes before the release. -- 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
