janhoy commented on PR #3044: URL: https://github.com/apache/solr/pull/3044#issuecomment-3424032817
I had some work from months ago trying to parse the entire CHANGES.txt to convert to yaml. At that time I tried feeding our perl script into Gemini to convert it to python, but it failed. So today I decided to work with Claude Code to see what could be done. Together we wrote a python script [dev-tools/scripts/changes2logchange.py](https://github.com/apache/solr/pull/3044/files#diff-b90d978bfb615997bbf4c1244aabb999de44977ece8f603ae98b0b356f4f9ea1) which does advanced parsing of CHANGES.txt and spits out all the changelog folders with yaml in them and a `release-date.txt` file parsed from DOAP. ``` $ dev-tools/scripts/changes2logchange.py Usage: changes2logchange.py <CHANGES.txt> [<output_dir>] Arguments: CHANGES.txt Path to the CHANGES.txt file to migrate output_dir Directory to write changelog/ structure (default: ./changelog) ``` Running it yields ``` ============================================================ Migration Summary: Versions processed: 125 Entries migrated: 7033 Entries skipped: 0 Files created: 7033 Release dates written: 107 ============================================================ ``` Sample: <img width="513" height="340" alt="Skjermbilde 2025-10-21 kl 00 50 01" src="https://github.com/user-attachments/assets/17ef7344-491d-4398-bc39-a270e0662fb6"; /> It's 7033 files. I suggest that we do not check in all of them, but instead use the "archive" feature of logchange to generate a single `archive.md` file for all versions to and including 9.9.0 : ```bash logchange archive --version 9.9.0 ``` It looks like this, and the command `logchange generate` will concatenate those automatically: <img width="306" height="170" alt="Skjermbilde 2025-10-21 kl 00 56 16" src="https://github.com/user-attachments/assets/99bf029e-2f48-4e1b-97ca-7eaaf92037d8"; /> -- 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]
