c8330c9972
My original commit was somewhat more tongue in cheek, but I think this time I'm going to be honest, rather than hiding behind humor. I'm angry that we as a community have reached a point where we're falling apart because people would rather accept sealioning and bad faith arguments that belong in a 2002 mailing list, not a 2024 software community. Every time I dare come back to the Nix community as a more active contributor it feels like we have a fresh wave of controversy that we don't ever heal from, everyone just moves on, more tired, and more broken than before. And now it's crossed a line. I'm out. I hope the community decides to actually try and heal. Tolerating the intolerant for too long has consequences - and the [paradox of tolerance](https://en.wikipedia.org/wiki/Paradox_of_tolerance) has come to its natural conclusion here. If it does heal, I'll be back with a vengeance, because it turns out replacing Nix is hard - emotionally and technically, and I'll miss it. ~Danielle (this commit+PR are not a place for useless debates.) |
||
|---|---|---|
| .. | ||
| 3.5 | ||
| 3.4.nix | ||
| README.md | ||
README.md
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.