Hi, I'm almost done with the transition, but it's taking some time to consolidate branches etc. Even if CHANGES.txt is not yet gone, please contune adding your changelogs to the changelog/unreleased folder.
Jan > 22. okt. 2025 kl. 20:50 skrev Jan Høydahl <[email protected]>: > > Hi everyone, > > We're transitioning to logchange, an automated changelog generation tool. > Starting today, there's a six days transition period where you can add > changelog > entries using either the old CHANGES.txt method or the new logchange workflow. > On Tuesday, October 28th, CHANGES.txt will be removed and the new workflow > will > be mandatory across main, branch_10x, branch_10_0, and branch_9x. > > Why? The new workflow is more maintainable and reduces merge conflicts during > active development. > > What does this mean for you? Instead of editing CHANGES.txt, you'll create a > small > YAML file in the changelog/unreleased/ directory. The build system will > automatically > compile these into /CHANGELOG.md during release. For dev-docs on the new > process, see: > > https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc > > Questions? Feel free to reply to this thread or ask on Slack. > > Thanks, > David and Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
