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 commit * major versions N>=2 which do not resolve to a module which has /vN at the end of the module path will be required as +incompatible
On Wed, 28 Aug 2019 at 03:40, Jason E. Aten <j.e.a...@gmail.com> wrote: > > 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 unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/1801b795-ff54-425a-abc4-7ec28b0f679e%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CACoUkn7q8Np-v6Vb16Vo3Hg6%2BGQk43HAv0y-YROcvSTM4QAUgA%40mail.gmail.com.
