Go Modules on Badger and Dgraph

[adg (Andrew Gerrand)]

@francesc

I understand that changing the import path has benefits, but we also have other mechanisms to control this via Gopkg.toml , go.mod , or whatever flavor of requirements.txt we might be using. Wouldn’t that be enough? That would indeed “do less to enable more”, instead of (IMHO) artificially baking into Go Modules a best practice that not everyone follows.

It was a Go packaging best practice before it was a Go modules best practice. What about your users that don’t use dep? These breaking changes affect them too.

If you’re not concerned about those users, then why not make this new version of badger v1.6.0 instead of v2.0.0? Then you can make it a proper v1 Go module, and when you do decide to move to v2 then you can do it the proper Go module way.