Improve release notes

[francoisferrand]

Since we making many releases in objects team, it may be good to have actual release notes to be able to follow what is happening.

Due to the number of releases, this could be very time consuming; but since we are now using github actions, we may automate the release notes using Release Drafter : which automatically pickups and formats draft release notes as PR are merged (and which can thus be quickly published).

As an added bonus, it would be great if a release in github would "automatically" make the release in Jira and create the next version.

What do you think?

[miniscruff]

This might belong in Citadel more than Guidelines but not entirely sure myself on that one. Also very similar to my proposal here https://github.com/scality/citadel/pull/32 ( just using a different tool ).

[francoisferrand]

Not sure this is exactly the same topic : the discussion in that ticket is about a product's changelog (metalk8s), while my concern is about each component's changelog and avoiding having "empty" github releases by having a draft being automatically generated.

For products (ring, metalk8s, artesca, zenko ?) we should indeed spend the extra time required to make proper release notes; but not sure we can do this for each component.

[miniscruff]

The idea was to use Changie for both but more realistically component repositories. It does not really add any development time to create change fragments and it integrates well into CI to automate releases. This is one example from changie https://github.com/miniscruff/changie/releases/tag/v0.7.0 or you can reference the AWS JS SDK Changelog that uses a handmade tool very similar to Changie here https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md.