Release tag versioning

[GHkrishna]

What

Noticed a minor thing when creating tags,

If you have a look at the image above, the alpha tags v2.1.1-alpha.13 was created as an alpha for v2.1.1 but it never got into that version and would most likely go into the next version v2.1.2.

And also, would the more correct have been to name the beta tag v2.1.1-beta.4 as v2.1.2-beta.1?

[ajile-in]

Yes, a more logical release numbering would be helpful to avoid confusion.

When we promote an alpha 2.1.1-alpha.xx to the first beta the next natural tag is 2.1.1-beta.01

[GHkrishna]

Yes right.
And also one more think to note is that main releases, here 2.1.1 actually contains all the code on main branch irrespective of having a beta tag following the alpha tag.

In that case the beta was not required as all the code from previous releases is present in the release

[ajile-in]

Agree

[GHkrishna]

I just though over it and I believe the beta tag was created more as a means of deployment and as it didn't have anything to be a contender for the next release v2.1.2 the decision could've been made to version it the way it is, which makes sense.

I think the way to avoid this would be to always make sure that a main release is only made if we have a beta tag created right before it. Or we checkout to the beta tag and create the next release from it instead of the main branch