[REPO] - Create release guideline

[shenkeyao]

What is this task and why do we need to work on it?

We are creating releases/tags with different version incremental standards. It would be nice to have a standard on things like when to increment from 0.5.1 to 0.5.2 and when to 0.6.0.

What work will need to be done to complete this task?

No response

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

We have a clear guideline in GitHub on the release creation page.

Branch work will be merged to (if not the default branch)

No response

[shenkeyao]

Conclusions from Zulip discussion:

• Use -release to indicate a tag with a release.
  • E.g., 0.5.12-release.
• Append patch number for small revisions.
  • E.g., 0.5.12-release followed by 0.5.12.1, 0.5.12.2, etc., rather than immediately by 0.5.13.
• Increase the major number when there's a major release
  • E.g., For the next testnet Cappuccino, the version number should start with 0.6.