You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a +incompatible module decides to introduce a go.mod file and updates all of its import paths to include vX, what should their new git tag be? Should they bump their patch, minor, or major?
What version of Go are you using (go version)?
1.11
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
I briefly discussed this with Go team members at GopherCon but the question has come up a few times from library owners so I thought I'd create an issue for it.
Summary
When a +incompatible module decides to introduce a go.mod file and updates all of its import paths to include vX, what should their new
git tag
be? Should they bump their patch, minor, or major?What version of Go are you using (
go version
)?1.11
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?All
What did you do?
Introduce go.mod to a +incompatible package: google/martian#262
What did you expect to see?
A clear instruction on how to migrate such libraries.
What did you see instead?
I'm not sure if google/martian should go from
v2.0.0
tov2.0.1
orv2.1.0
orv3.0.0
The text was updated successfully, but these errors were encountered: