Skip to end of metadata
Go to start of metadata

Become a contributor

You need to be added as a contributor to edit the wiki. But don't worry! Just email any Mailing List or grab us on IRC and let us know your user name.

Supported Releases

1.6.0

May 6th, 2014

apache-couchdb-1.6.0.tar.gz [ OpenPGP ] [ MD5 ] [ SHA ]

1.5.1

March 27th, 2014

apache-couchdb-1.5.1.tar.gz [ OpenPGP ] [ MD5 ] [ SHA ]

1.5.0 

November 6th, 2013  

apache-couchdb-1.5.0.tar.gz [ OpenPGP ] [ MD5 ] [ SHA ]  

Release Support Policy

  CouchDB uses semantic versioning, so, in a nutshell:  

  • X.Y.Z equates to major version, minor version, and patch version. 
  • 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

 Old Apache CouchDB releases can be found in the Apache CouchDB archive.  

Even older Apache Incubator releases of CouchDB can be found in the Apache Incubator archive of CouchDB.  

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.  

You can check the OpenPGP signature with:  

You can check the MD5 checksum with:  

You can check the SHA checksum with:  


  • No labels