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

Consider tagging module "go"? #56

Open
Rick-xuy opened this issue Feb 18, 2023 · 0 comments
Open

Consider tagging module "go"? #56

Rick-xuy opened this issue Feb 18, 2023 · 0 comments

Comments

@Rick-xuy
Copy link

I found that go packages, say github.com/cncf/xds/go/udpa/annotations, are placed in submodule github.com/cncf/xds/go.

However, it seems that module github.com/cncf/xds/go is not tagged. According to Go Modules wiki, submodule should be tagged like relative-path-to-root/vX.X.X.
At now, when trying to import package github.com/cncf/xds/go/udpa/annotations, downstream would depends on pseudo-version of module github.com/cncf/xds/go.

github.com/cncf/xds/go v0.0.0-20211001041855-01bcc9b48dfe

I think it is not very readable and difficult to upgrade. This is not conductive to version control either.
So, I propose whether it is possible to tag submodule properly to better support go users. For example, go/v0.0.1, go/v1.0.0etc, so that other project can use tag to import this module in go.mod.

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