Note that the upgrade path for minor versions is to update the latest minor version. We will not continue to release bugfix versions for an old minor version. That is, 1.1.0 immediately supersedes 1.0.x, and no more fixes will be made on the 1.0.x line. Similarly, 1.2.0 immediately supersedes 1.1.x.

Note that the upgrade path for minor versions is to update the latest minor version. We will not continue to release patch versions for an old minor version. That is, 1.1.0 immediately supersedes 1.0.x, and no more fixes will be made on the 1.0.x line. Similarly, 1.2.0 immediately supersedes 1.1.x.

We have a new wiki. The migration is not 100% complete. You can help out by moving pages across. This wiki will exist for as long as there are pages left.

The official documentation has moved to http://docs.couchdb.org — The transition is not 100% complete, but http://docs.couchdb.org should be seen as having the latest info. In some cases, the wiki still has some more or older info on certain topics inside CouchDB.

Release Support Policy

The major version will be incremented every time we make backwards incompatible changes.

The minor version will be incremented every time we add backwards compatible features.

The patch version will be incremented every time we add backwards compatible fixes.

We will support each major version for 12 months. So, if 1.0.0 was released on 2010-01-01, then we would add features and fixes to it until 2011-01-01. After 12 months have passed, we may continue to release fixes for critical security issues, but these will be in the form of actual patches.

Note that the upgrade path for minor versions is to update the latest minor version. We will not continue to release patch versions for an old minor version. That is, 1.1.0 immediately supersedes 1.0.x, and no more fixes will be made on the 1.0.x line. Similarly, 1.2.0 immediately supersedes 1.1.x.

Archived Releases

These are provided for reference purposes only. It is recommended you use a current release of CouchDB.

Verifying Releases

When downloading from a mirror please check the MD5 and SHA checksums as well as verifying the OpenPGP compatible signature available from the main Apache site. The KEYS file contains the public keys used for signing release. It is recommended that a web of trust is used to confirm the identity of these keys.