when is the next release?

[h8liu]

people are starting to use go modules, but can only use a release before the import path has changed. This has caused incompatibility between go get with modules enabled or not.

See google/go-cloud#429 for background.

Is there planning/timeline for a release 4.0.0 (because import path change is not backward compatible now)?

[gyuho]

Yeah for v3.4, I will soon switch to go module. Already tried it and works well for etcd.

[h8liu]

note that, based on semver spec, after the import path change to go.etcd.io/etcd, the version number probably, needs to be 4.0

[gyuho]

@h8liu I don't think we need bump up major version? It's only import path change, no API change was made.

[h8liu]

because of the import path change, previous code that imports "github.com/coreos/etcd" won't be able to use the code without change. For example:

https://gopkgs.io/builds/20180911-195307-3d66b81f

unless you treat it a completely different package.. where the new version number does not matter.

[xiang90]

@h8liu

The etcd version is not going to get bumped. etcd is a binary program not a library. We have been talking about how to separate the client library versioning from the etcd binary versioning, but have not found a good way to do it.

[wenjiaswe]

cc @jpbetz

[h8liu]

@xiang90 Thanks for explaining. Then it is wrong for go-cloud (or any repo that uses go mod from 1.11) to reference the version in its go.mod or go.sum.