New release process expectations from the community

[kavirajk]

@trevorwhitney is working on new release process using Github Actions and release-please tooling.

The new release process automation uses conventional commits to generate the changelog entries automatically. So here are the expectations from the community once new release process is integrated.

1. Use conventional commits for all your commits
2. DO NOT add CHANGELOG entry when create a PR.

[periklis]

As mentioned elsewhere, I would like to note that we are super interested to move/replicate the manual release process to the new release-please/whatever-tool based approach also for the Loki Operator.

[kavirajk]

FYI: @trevorwhitney in-fact tested 2.9.5 patch release with this new workflow. Details on this PR. cc @periklis

[trevorwhitney]

@periklis you can find the new workflow here: https://github.com/grafana/loki/actions/workflows/patch-release-pr.yml, using workflows/actions from https://github.com/grafana/loki-release. There area few rough edges to sand off to get it fully integrated (for example there's been drift in our linting from when I started, as the GH action linter is no longer agreeing with the Drone one it seems). The hope is we can test this on a 2.9.5 soon.

[frittentheke]

This is an awesome push 👍

Release early. Release often. And listen to your customers.
(http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html)