prudhvigodithi commented on issue #15421: URL: https://github.com/apache/lucene/issues/15421#issuecomment-3590166724
I have an idea, how about we simplify `CHANGES.txt` to track only the upcoming release version per branch? Since the repo is already branched by version we can: - `main` → `CHANGES.txt` tracks only upcoming version changes - `branch_10_3` → `CHANGES.txt` tracks only upcoming 10.3.x changes Contributors can simply append to `CHANGES.txt` instead of searching through the entire file to find the right version section. Now we can use `CHANGES.txt` from that branch directly as release notes (no need to scan commits or PRs as the file already has exactly what's in this release). Only catch here is to clear `CHANGES.txt` to start fresh for the next release, IMO we should be able to automate this with a workflow to create a PR with clearing `CHANGES.txt` on a release event. Clearing `CHANGES.txt` after release should be fine as the content is preserved in the tagged release. So : - Now since file is not too large users can just add content to the `CHANGES.txt` in one section. This is applicable for each version branch. - Release workflow can use this `CHANGES.txt` as the release notes. - Clear the `CHANGES.txt` as the content is saved in the release tag and start fresh. I also noticed one thing the `main` now tracks both `11.0.0` and `10.4.0`, we should create the `branch_10_4` early (I'm not sure today when we create the `branch_10_4`) and follow the same pattern the `branch_10_4` will now have `CHANGES.txt` that only tracks `10.4.x`. -- 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]
