adRise/update-pr-branch

Taging convention to follow the major and minor tags to point to patch

Opened this issue · 3 comments

Hi,

By following this concept of tagging, we could use e.g @v0 or @v0.7 in our workflow files and your backward compatible changes would always used automatically. Little bit of extra work at the time of release, less maintenance at user side.

Thanks for considering

Hi @KissPeter , can you elaborate? These are the current tags now. What does the expected list look like?

image

Hi,
Sorry about the late reply.
If you had a v0.7 tag which is pointing to the most recent V0.7.* version, at our side we would not need to make any change at minor version change, we would automatically use the most recent version
So the process would be something like this:

  • We have v0.7 pointing to v0.7.1
  • New release is ready, you roll it out as v0.7.2 and update v0.7 to point to the commit of v0.7.2.

Thanks

@KissPeter oh, I see your points. Thank you for the explanation. We will do some investigation