First, I’d suggest following a commit message convention. You may define your own or follow an existing one such as https://www.conventionalcommits.org/en/v1.0.0/
Next, use a tool that can read, parse, and format commit messages. You’ll find plenty of options out there. I can pitch https://jreleaser.org/ 😉 Cheers Andres Sent from my primitive tricorder > On 13 Mar 2024, at 23:58, Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > > Hi, > > Today's facts: > > - We manage our issues in jira and all officala release notes are also in > jira. > - We sent an email in text format to announce mailing list. > - In project documentation we don't have a release notes > > But as we see in: > https://lists.apache.org/thread/pzd36lo6rtfn7c5s0x60xbj296xt1mvf > today it is not a user-friendly way. > > It looks as most usable will be to manage release notes also in GitHub at > least as link to jira public url for release notes. > Yes I know we don't have (or have old one like maven-changes-plugin) > perfect tools to help with this process. > > Any other propositions, ideas ....? > > -- > Sławomir Jaranowski
