646b892680
Some checks failed
Periodic Merges (6h) / master → staging-nixos (push) Failing after 12m50s
Periodic Merges (6h) / master → staging-next (push) Failing after 12m54s
Periodic Merges (24h) / merge-base(master,staging) → haskell-updates (push) Failing after 11m54s
Periodic Merges (6h) / staging-next → staging (push) Failing after 12m13s
Periodic Merges (24h) / staging-next-25.05 → staging-25.05 (push) Failing after 13m24s
Periodic Merges (24h) / release-25.05 → staging-next-25.05 (push) Failing after 14m28s
27 lines
913 B
Markdown
27 lines
913 B
Markdown
# etcd
|
|
|
|
|
|
## Upstream release cadence and support
|
|
|
|
The etcd project maintains release branches for the current version and previous release.
|
|
|
|
For example, when v3.5 is the current version, v3.4 is supported. When v3.6 is released, v3.4 goes out of support.
|
|
|
|
Reference: https://etcd.io/docs/v3.5/op-guide/versioning/
|
|
|
|
|
|
## NixOS release and etcd version upkeep
|
|
|
|
Every major/minor version bump of `etcd` top-level alias in nixpkgs requires a notification in the next NixOS release notes scheduling the removal of the now unsupported etcd version.
|
|
|
|
After every NixOS release, the unsupported etcd versions should be removed by etcd maintainers.
|
|
|
|
|
|
## User guidelines on etcd upgrades
|
|
|
|
Before upgrading a NixOS release, certify to upgrade etcd to the latest version in the current used release.
|
|
|
|
Manual steps might be required for the upgrade.
|
|
|
|
NixOS release notes might have instructions on how to proceed on upgrades.
|