Document release policy

[jsoref]

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [x] I've included steps to reproduce the bug.
• [ ] I've pasted the output of argocd version.

Describe the bug

There's no official published document about when releases happen

To Reproduce

See people asking "when is the next release going to happen"

• https://argoproj.slack.com/archives/CEWCP8TV5/p1613597871118200?thread_ts=1613591956.115200&cid=CEWCP8TV5

Expected behavior

argocd makes releases when a version’s milestone tasks are complete — see the <…milestone-link…> page to see the tasks that are blocking the next release. in the Release policy section on the roadmap document in the docs

Screenshots

Version

Paste the output from `argocd version` here.

Logs

Paste any relevant application logs here.

[jsoref]

• The release process for a new release starts roughly when items planned for the current in progress release are complete
• there's a branching step
• alpha/beta/rc candidates, testing
• and following the steps in https://github.com/argoproj/argo-cd/blob/master/docs/developer-guide/releasing.md