Version 3.3.12 home Download and build Libraries and tools Branch management Demo Discovery service protocol Frequently Asked Questions (FAQ) Logging conventions Metrics Production users Reporting bugs Tuning etcd release guide Benchmarks Benchmarking etcd v2.1.0 Benchmarking etcd v2.2.0 Benchmarking etcd v2.2.0-rc Benchmarking etcd v2.2.0-rc-memory Benchmarking etcd v3 Storage Memory Usage Benchmark Watch Memory Usage Benchmark Developer guide Experimental APIs and features Interacting with etcd Set up a local cluster System limits Why gRPC gateway etcd API Reference etcd concurrency API Reference gRPC naming and discovery Learning etcd client architecture Client feature matrix Data model Glossary KV API guarantees Learner etcd v3 authentication design etcd versus other key-value stores etcd3 API Operations guide Clustering Guide Configuration flags Design of runtime reconfiguration Disaster recovery Failure modes Hardware recommendations Maintenance Migrate applications from using API v2 to API v3 Monitoring etcd Performance Role-based access control Run etcd clusters inside containers Runtime reconfiguration Supported systems Transport security model Versioning etcd gateway gRPC proxy Platforms Amazon Web Services Container Linux with systemd FreeBSD Upgrading Upgrade etcd from 2.3 to 3.0 Upgrade etcd from 3.0 to 3.1 Upgrade etcd from 3.1 to 3.2 Upgrade etcd from 3.2 to 3.3 Upgrade etcd from 3.3 to 3.4 Upgrade etcd from 3.4 to 3.5 Upgrading etcd clusters and applications etcd v3 API

Branch management




  • New development occurs on the master branch.
  • Master branch should always have a green build!
  • Backwards-compatible bug fixes should target the master branch and subsequently be ported to stable branches.
  • Once the master branch is ready for release, it will be tagged and become the new stable branch.

The etcd team has adopted a rolling release model and supports two stable versions of etcd.

Master branch

The master branch is our development branch. All new features land here first.

To try new and experimental features, pull master and play with it. Note that master may not be stable because new features may introduce bugs.

Before the release of the next stable version, feature PRs will be frozen. A release manager will be assigned to major/minor version and will lead the etcd community in test, bug-fix and documentation of the release for one to two weeks.

Stable branches

All branches with prefix release- are considered stable branches.

After every minor release (, we will have a new stable branch for that release, managed by a patch release manager. We will keep fixing the backwards-compatible bugs for the latest two stable releases. A patch release to each supported release branch, incorporating any bug fixes, will be once every two weeks, given any patches.

© 2019 The etcd authors

Branch management