What's the plan for version 3.5? When will it be released?

[Jayden-onl]

As we know, the package management of recent versions is not good.
The version of grpc also old.
When will version 3.5 be released?
😂

[mlboy]

+1

[dmitris]

there's a little bit of discussion of 3.5 in https://www.youtube.com/watch?v=SqfxU9DhBOc&feature=youtu.be

Maybe it would be possible to create something like Release-3.5 or Milestone-3.5 label to group the related issues and to give a bit more visibility on what's still in flight, where help could be needed (ex. with testing) etc.?

/cc @gyuho

[mlboy]

The label has created which is named "area/clientv3", And milestone is "etcd-v3.5".
But, I anxiously hope that put it on schedule.

[sagikazarmark]

There is a milestone for 3.5: https://github.com/etcd-io/etcd/milestone/37

A lot of issues are still labeled as "Investigating" though.

[sagikazarmark]

Let's say 3.5-alpha gets released soonish (#12498). What does that mean for the stable 3.5 release?

As I mentioned in the linked issue, half the world depends on etcd (either directly or transitively) and libraries probably won't upgrade to an alpha version, so the situation won't be resolved with an alpha release. It'll probably be a great demonstration of the release script, though.

So the question is: what comes after the alpha version?

As far as I can see, there is a gRPC upgrade issue that's also close to being resolved. Is there anything else that blocks a stable version other than an alpha testing period? If not, would it be possible to set a deadline for the alpha testing period and (if nothing comes up) just tag a release when that deadline is over?

WDYT @ptabor @gyuho ?

If not, what's the timeline that we can expect? I imagine there are a lot of parties to coordinate with (Kubernetes being a prominent one), but etcd 3.5 has been stalled enough despite bringing the (IMHO) most important improvement for ecosystem in a long time, so it'd be really great if you could shed some light on the future of etcd 3.5.

Thanks a lot for the hard work you are doing!

[ptabor]

I'm all for releasing (and getting feedback) frequently.
Looking at the list https://github.com/etcd-io/etcd/milestone/37 I think most of this issues are 2017-2018 and looks like carry-over.

@maxenglander owns the most-recent issues (auto-promoting nodes). Do you plan to work on them ?

Personally 3.5-stable I would scope to:

• P0 Finish the grpc stuff
• P1 Reduce etcd dependency on store v2 #12800 make sure v2-store can be opted-out to unblock perf-gains & decomissioning this code in 3.6.
• (optional) P2 subsplit proxy code to separate module (opt-in binary)
• (optional) P2 subsplit etcdadm code to separate module (opt-in binary)
• (optional) Move big parts of clientv3/server code to 'internal' subdir [such its known what's implementation detail]
  But also fine with calling a release calendar for early Q2 and taking whatever is on time.

[maxenglander]

Hey @ptabor I would like to continue working on auto-promoting nodes. I have a proof-of-concept implementation (#10887), but I am waiting for a review of etcd-io/website#107 (migrated from #10913) before going further. Thanks!

[sagikazarmark]

Checking in to see if there is an update on a 3.5 release date.

I've updated etcd in Dex, Viper and go-kit (in Draft PRs) and they seem to be working as expected (go modules work, e2e tests passed).

[sagikazarmark]

The community meeting notes mention "Mid May" as a rough timeline / feature-freeze timeline. What does that mean exactly? Is that an estimated release date? Or is it just a target for feature freeze and release will happen somewhere in the future following that?

[gyuho]

We have quite a few milestones left https://github.com/etcd-io/etcd/issues?q=is%3Aopen+is%3Aissue+milestone%3Aetcd-v3.5

• *: define strict TLS 1.2 cipher suite default #10304
• Support client configuration via environmental variables #12785
• Use Go 1.16 for 3.5 release and testing #12732

[liggitt]

I'm also interested in this, since v3.5.0 unblocks grpc dependency upgrades (xref kubernetes/kubernetes#100488)