Revision 58455a2ae4ec358f7f9915cc012a7addead4c152 authored by Yicheng Qin on 26 August 2015, 04:59:56 UTC, committed by Yicheng Qin on 26 August 2015, 05:04:26 UTC
Or it may panic when new transport fails, e.g., TLS info is invalid.
1 parent 6250fed
ROADMAP.md
# etcd roadmap
**work in progress**
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.
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 3.0 (January)
- v3 API ([see also the issue tag](https://github.com/coreos/etcd/issues?utf8=%E2%9C%93&q=label%3Av3api))
- Transactions
- Leases
- Binary protocol
- Support a large number of watchers
- Better disk backend
- Improved write throughput
- Support larger datasets and histories
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...