beta version 0.1 and 0.2 about gopkg HOT 1 CLOSED

If you follow semantic versioning, v0 is allowed to break compatibility and people will just have to update. That's used for highly unstable software that you don't want to promise any guarantees just yet.

That said, you seem to be bothered by the breakage, which implies that's now quite what you expected or intended to offer. In those cases, the common convention in semantic versioning and in good part of the software world is to respect compatibility across version updates when you're just bumping a minor version. That's why we support v0, v1, etc as separate URLs. People using one of those is guaranteed to stay safe since the author shouldn't be breaking backwards compatibility inside the major.

There are some more details in this post which will probably be an interesting read:

https://blog.labix.org/2015/01/14/no-minor-versions-in-go-import-paths

from gopkg.