Re: User friendly release notes

[Timothy Stone]

On 3/13/24 7:05 PM, Andres Almiray wrote:

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/

+1

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/ 😉

Not familiar with jreleaser. I will say that mixed technology pipelines have worked well for us, with Node managing many aspects of versioning and providing previous/next versions to the Maven Release Plugin via the pipeline environment.

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.

... snip

Any other propositions, ideas ....?

--
Sławomir Jaranowski

--
Timothy Stone
=============
Some call me ... Tim.
Husband, Father, Blogger, OSS, Wargamer, Home Brewer, and D&D
Find me on GitLab | GitHub | Linked In | MeWe | GnuPG

OpenPGP_signature.asc
Description: OpenPGP digital signature