jlhawn
commented
6 years ago I'm certainly not the final authority on it, but I do not expect anyone to be actively addressing issues and new pull requests on this repository. My recent contribution was just done to address outstanding issues in one of our commercial products which still uses components which depend on this library. Internally at Docker, we only have products which use the the etcd libkv backend (and still only use the v2 api).
I believe folks from Docker originally began this project as a component of Docker Swarm so that it could be used with multiple key-value stores. While that project is still maintained, there's not been much new feature development there (mostly just bug fixes in order to address issues with Docker's commercially-supported products) and it is not recommended for new Docker users in favor of the newer built-in orchestration features of Docker over the past year. Most of Docker's orchestration development efforts have been focused on those built-in SwarmKit orchestration features and more recently in integrating Kubernetes into the Docker platform.
I would suggest using @abronan's fork (https://github.com/abronan/libkv) for any new projects. He was previously the most active maintainer on this library and it seems he and several others have been actively maintaining that fork. It also includes part of the etcd v2 fix I had worked on here and even has a newer etcd v3 backend and a redis backend.
mthenw
Hey @jlhawn & @vieux, I have a quick question. What's the status of this package? Are you planning to be more active in terms of merging PRs and adding requested features?