I followed up with a JIRA issue https://issues.apache.org/jira/browse/SOLR-17619 and also filed an issue on the logchange project to support Gradle: https://github.com/logchange/logchange/issues/397 at least for adding new change entries conveniently. That might be considered a blocker as we need/want creating new entries to be super easy.
On Fri, Dec 20, 2024 at 4:43 AM Jan Høydahl <jan....@cominvent.com> wrote: > Good news, a new release is on its way, including a CLI tool < > https://github.com/logchange/logchange/pull/31> independent from maven. > This means we could integrate it into our process with simple commands like > ./logchange release --version 9.8.0 > ... which will move yml files from folder "unreleased" into folder "v9.8.0" > and then generate CHANGELOG.md with ./logchange generate. > > See https://github.com/logchange/logchange/tree/main/changelog for how the > strucuture looks like. > > Jan > > > 19. des. 2024 kl. 20:34 skrev David Smiley <dsmi...@apache.org>: > > > > On Wed, Dec 18, 2024 at 7:30 PM Jan Høydahl <jan....@cominvent.com> > wrote: > > > >> This tool does what is proposed here and looks promising: > >> https://github.com/logchange/logchange?tab=readme-ov-file > >> > >> It requires us to switch to CHANGES.md and it lacks a gradle plugin. But > >> we could probably contribute some changes to fit our needs.. > >> > > > > We don't require a gradle plugin. Arguably it should have been done as > > simple scripts without being tied to any build system. There's even a > TODO > > on its main page that refers to a Docker version. I could imagine one of > > us essentially doing this (creating the Dockerfile and any scripts) so > that > > it can more easily be run; maybe tailored for us. > >
