As far as I understand it - github.com/user/foo is expected to house package foo for SemVer 0.x.x – 1.x.x - github.com/user/foo/v2 is expected to house package foo for SemVer 2.x.x - github.com/user/foo/v3 is expected to house package foo for SemVer 3.x.x
And so on. Appending the additional path is optional in the sense that consumers can still lock to package foo at v2.3.4 if it lives in plain github.com/user/foo, but that lock will be expressed in the so-called psuedoversion form "v0.0.0-timestamp-revhash". On Tue, Feb 20, 2018 at 4:56 PM, Jon Calhoun <joncalh...@gmail.com> wrote: > Would you be willing to create an example illustrating how a versioned > package should look with major version changes? You have great examples for > the minor/patch changes, but I don't see any concrete examples for a major > version bump. > > On Tuesday, February 20, 2018 at 12:20:54 PM UTC-5, Russ Cox wrote: >> >> Hi everyone, >> >> I have a new blog post you might be interested in. >> https://research.swtch.com/vgo. >> >> I'll try to watch this thread to answer any questions. >> >> Best, >> Russ >> >> >> > -- > 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. > For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
