Re: [go-nuts] Re: how to create path/v2 and path/v3 and path/v4 in same repo

The short version is: * semantic version git tags are the means of releasing new versions * you can follow whatever strategy you like when it comes to maintaining multiple major versions of a module (you might not need to); branch, subdirectory... Just so long as the git tag gets you to the right

Re: [go-nuts] Re: how to create path/v2 and path/v3 and path/v4 in same repo

Thanks guys. https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher seems to say that the answer is yes, but that it won't be backwards compatible with tags and go.mod alone. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To

Re: [go-nuts] Re: how to create path/v2 and path/v3 and path/v4 in same repo

To add to Chris' response also see the wiki https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher Also see https://github.com/golang/go/issues/33637 for details on how modules documentation will be getting a revamp in 1.14. On Tue, 27 Aug 2019 at 12:49, Chris Hines wrote: > >

[go-nuts] Re: how to create path/v2 and path/v3 and path/v4 in same repo

You might be able to find an answer to your question in this article: https://github.com/go-modules-by-example/index/tree/master/016_major_version_repo_strategy On Tuesday, August 27, 2019 at 6:31:57 AM UTC-4, Jason E. Aten wrote: > > With an eye towards implementing semantic import path versioni