docs: Update the release guide for creating/pushing tags

[rnishtala-sumo]

Update the release guide for creating/pushing tags

• Release guide change to avoid tags from being created on main and instead only create tags on release branches.

• Documentation updated

[sumo-drosiek]

We don't want to tag a release branch (with major releases), as git hash is going to give us wrong value if it won't be on main branch.

This is quite painful and not intuitive that the release branch has already additional commit which is not tagged, but at least CI and builds are being created properly

[rnishtala-sumo]

I didn't think that git hash depended on a branch. Just did a quick search on this and this popped up.

A commit hash depends on

• The commit message
• The file changes
• The commit author (and committer- they can be different)
• The date
• The parent commit hash

As long as we have the correct list of commits in the release branch, it seems like we should be able to push a tag on this branch and create a release, irrespective of major, minor or patch?

[sumo-drosiek]

Oh, sorry, I meant git describe:

> git describe --tags              
v3.9.1-7-gd373d1ca

it relies on commits history, so if we tag outside of branch, we always get v3.9.1-...

[rnishtala-sumo]

yes that's true, so all the patch release tags would be on the release branch and all the major/minor release tags would go on the main branch.

[sumo-drosiek]

yes that's true, so all the patch release tags would be on the release branch and all the major/minor release tags would go on the main branch.

Yes, exactly

[sumo-drosiek]

@rnishtala-sumo can we close it?