Improvements in release process & management

[laumair]

Description

I think we need to think about the improvements in our current release process management. From my perspective, we need the following changes:

1. Remove Apply version updates from release PRs and releases. The wording is a bit unclear. Instead use something else that is clearer;
2. Always have a change log associated with a release. Do we need to make changes in a workflow for that?
3. For all older releases, can we manually add a change log?
4. Document our current release process. It should reflect the following:
   • What are the steps we need to take for releasing a new major / minor / patch version?
   • What warrants a new release?
   • How should the versioning be done?
   • Do we need monthly releases?
   • Define a checklist of smoke tests that should be performed before every release.
   • Define how the release should be announced. Since, lots of projects / applications are using this package, we need to define a solid process so that everyone using this can update in time.
   • How to release / announce a security critical release?
   • How to manage alpha / beta / production version of the releases? Ideally, every release should not be directly pushed to production. Instead, there should be a well defined process of testing before it can be released to production.
5. Define a process for what warrants a security audit before release.

Motivation

In my opinion, the definitions of these processes are much needed. Currently, it is very ad-hoc in nature.

Open questions (optional)

Happy to hear everyone thoughts on this.