docs(release): add information on how we tag and release

[gustavovalverde]

Motivation

We want to document the process we decided for audits and new features. We also want to write down the goals we're trying to satisfy.

Closes #5259

Solution

Improve the documentation from our Zebra versioning and releases

Review

This is a draft for revision. I started a whole document but then I realized I was repeating most of the information already available in the Release process and the release checklist

As @arya2 and @teor2345 recently made the first release candidate, they might have more fresh ideas to add here.

Reviewer Checklist

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info? (new features, breaking changes, large changes)
• Are the PR labels correct?
• Does the code do what the ticket and PR says?
• How do you know it works? Does it have tests?

[teor2345]

Looks good!

We talked about audit tags and audit branches, but they aren't mentioned in this document.
Can you add a short section based on what we decided in the meeting:

• we'll give the latest rc tag to the auditors to review
• when we get the audit report, if the auditors want to review a separate branch with just the audit fixes, we'll make a branch from the audit tag, and make fixes there

[teor2345]

@gustavovalverde did you want help with the audit part, or did you want to do that in a separate PR?

[gustavovalverde]

@gustavovalverde did you want help with the audit part, or did you want to do that in a separate PR?

I created a ticket for the specific audit part #5431

[teor2345]

@gustavovalverde did you want help with the audit part, or did you want to do that in a separate PR?

I created a ticket for the specific audit part #5431

Fair enough, I think that will also be partly covered by #5395, which mentions the audit tag and dependencies.

[teor2345]

Thanks!