Releases timeline

[fntlnz]

What would you like to be added:
After discussing with everyone on slack we came up with the fact that our community needs a public release timeline that can effectively communicate when future releases are expected to happen.

For example we can have a 3 month cadence with bug fixing and minor releases between them.

Another requirement that came up is that when we start the release timeline we will need to put the old releases in it, so not only showing a timeline for future releases but reconstructing the timeline for releases we already did.

Citation from Fahad in the public slack:

regular release cadence sets the expectations with downstream users (indirectly implies higher satisfaction score). That being said, a process/strategy for hot-fixes/quick-emergency-releases is a bonus too!

Why is this needed:

Because we need to be transparent in doing the release process so that everyone can build expectations on them, both users and contributors.

[fntlnz]

Related to: #726

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.