prudhvigodithi commented on issue #15421: URL: https://github.com/apache/lucene/issues/15421#issuecomment-3608598942
> Not totally opposed to the idea of dividing `CHANGES.txt` across branches Right, if we migrate CHANGES.txt per release model provided it gives more structured management, we can still grep for each tag and consolidate. I'm not sure how this works today https://lucene.apache.org/core/10_3_2/changes/Changes.html#older but in order not to break this we can have a workflow that generates a consolidated `CHANGES.txt` and park it in the repo. -- 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]
