... not sure if that helps but i had some minutes time ... cheers lenz On Sat, Jan 17, 2009 at 7:33 AM, Damien Katz <dam...@apache.org> wrote: > > - Community
The community around CouchDB grew in the last couple of months quite a bit. We gain attention in early adaptor markets and can look at the first production grade setups running on CouchDB (iWantMyName, pcapr.net<http://www.pcapr.net>). The mailing list traffic grew and so did the number of third party library implementations that interact with CouchDB. More and more support on the mailing list comes from outside the core team which proves that there is an active community growing. Many projects in the early adopter space start using CouchDB from languages such as ruby, perl, python and erlang. A simple search on github reveals around 30 projects around CouchDB. > > > This needs some stuff! > > > - Development > > We are now looking to release CouchDB 0.9.0 in January, our first as TLP > and our first BETA release . > > New features currently in trunk for 0.9.0: > - Security and data validation functionality > - View server internals re-architecture to allow the ability to quickly > read stale views as indexes are being updated. > - Multi-key view lookup enhancements > - Include_docs. Ability to load full documents with view rows. > - Btree performance improvements > - Faster and more compact internal JSON term format, that is also the new > Erlang canonical JSON term format. Additionally, when a low level JSON > parser is implemented in core Erlang, it is will use this format and we'll > gain more performance for free. > - Ability to run a CouchDB server right from the project source directory, > for development purposes > - Streaming attachment writes > - fliters for converting json documents to other formats (XML, HTML, etc) > - Deferred commits (optional acid) for faster update and replication speed > > > - Infrastructure > > We have now transfered all couchdb assets over to the final TLP locations, > including the couchdb.apache.org site, the mailing lists and the SVN > repositories. >