Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
KissPeter opened this issue Mar 6, 2024 · 3 comments
Open

Comments

@KissPeter
Copy link

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

@zhiyelee
Copy link
Collaborator

zhiyelee commented Apr 18, 2024

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

image

@KissPeter
Copy link
Author

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

@zhiyelee
Copy link
Collaborator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants