|
@@ -6,21 +6,7 @@ This document defines a high level roadmap for etcd development.
|
|
|
|
|
|
|
|
The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project. The [milestones defined in GitHub](https://github.com/coreos/etcd/milestones) represent the most up-to-date and issue-for-issue plans.
|
|
The dates below should not be considered authoritative, but rather indicative of the projected timeline of the project. The [milestones defined in GitHub](https://github.com/coreos/etcd/milestones) represent the most up-to-date and issue-for-issue plans.
|
|
|
|
|
|
|
|
-etcd 2.0 is our current stable branch. The roadmap below outlines new features that will be added to etcd, and while subject to change, define what future stable will look like.
|
|
|
|
|
-
|
|
|
|
|
-### etcd 2.2 (September)
|
|
|
|
|
-- Improve client libraries
|
|
|
|
|
- - Go
|
|
|
|
|
-- Improve documentation
|
|
|
|
|
-- etcdctl
|
|
|
|
|
- - use new etcd client
|
|
|
|
|
-- Stats and Metrics
|
|
|
|
|
- - Standardize endpoint for gathering metrics
|
|
|
|
|
- - Health and status endpoints
|
|
|
|
|
-- Add benchmarks for our future targets
|
|
|
|
|
-- V3 API preview
|
|
|
|
|
- - non-clustered version
|
|
|
|
|
- - support gRPC based key API
|
|
|
|
|
|
|
+etcd 2.2 is our current stable branch. The roadmap below outlines new features that will be added to etcd, and while subject to change, define what future stable will look like.
|
|
|
|
|
|
|
|
### etcd 3.0 (January)
|
|
### etcd 3.0 (January)
|
|
|
- v3 API ([see also the issue tag](https://github.com/coreos/etcd/issues?utf8=%E2%9C%93&q=label%3Av3api))
|
|
- v3 API ([see also the issue tag](https://github.com/coreos/etcd/issues?utf8=%E2%9C%93&q=label%3Av3api))
|
Yicheng Qin