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

Move v1 tag to latest v1.x release, similar for v2 tag #10

Open
mgeisler opened this issue Apr 4, 2023 · 0 comments
Open

Move v1 tag to latest v1.x release, similar for v2 tag #10

mgeisler opened this issue Apr 4, 2023 · 0 comments

Comments

@mgeisler
Copy link

mgeisler commented Apr 4, 2023

Hi there!

This is slightly related to the discussion in #1: I believe the v1 tag should be moved to point to the same commit as the v1.6 tag. Similarly, l believe it's good practice to have a v2 tag that would point to the same commit as the v2.2 tag.

This would make it possible for people to track the v2 line of releases. This in turn will lead to less churn for the wider community. Currently, they can only track a single tag and they're all different:

The GitHub documentation describes this in a bit more detail.

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

1 participant