Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C5A9F953 for ; Wed, 3 Apr 2013 07:46:09 +0000 (UTC) Received: (qmail 41098 invoked by uid 500); 3 Apr 2013 07:46:07 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 41042 invoked by uid 500); 3 Apr 2013 07:46:07 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 40997 invoked by uid 99); 3 Apr 2013 07:46:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 07:46:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dch@jsonified.com designates 209.85.215.48 as permitted sender) Received: from [209.85.215.48] (HELO mail-la0-f48.google.com) (209.85.215.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 07:46:00 +0000 Received: by mail-la0-f48.google.com with SMTP id fq13so1162440lab.35 for ; Wed, 03 Apr 2013 00:45:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jsonified.com; s=google; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=1xIyNB2eP5SOJmeKkJstuUpyONX5Id4diZphrfRZYZQ=; b=L4fyIcCIdgPTygKJKwtAJv5YugseDczqkA/bONtHAHcoDODBIyP2Qo+Lt5TN2bACEC e+b3zgMnJb+uGLR7vzi4yYEUG00FPtiXCYoBa2MI0VYppaOzsBTQfMPE9cUC141Uu/MK dCH0Rg92DaUg/LnHKQoYPR4JJrSO2n1mgB2jM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=1xIyNB2eP5SOJmeKkJstuUpyONX5Id4diZphrfRZYZQ=; b=VOJaUyi+29ePH0iFQRuBW6NxXIVviR1Ls2yoH8jxNlQ7pAfoLd4anm+14wDFjdvCrU eZLyH2P2PRbjBVFI6hdiqocOa1Ust2WwZiBAlacAZrR8BR9YIVIHYlJVf6NFNfyGkCf+ 2jA1aijao9KI3vlx9tN/sKjv5Iur1L5JuMnV5lvTpwzMqy3rsDPFc0zOMJjNy+v/IznK HCEFzsUFGaBwjwla1ZtcZq+TtyxEYb0cEvwCvwtQ1M/1ZMSZ3KS2ycY4XfM6kOrsVPBM QXpGZpUjA3uvlVrXHliACcQHdwmbBhcIndOu5r4OsXfmCt5IjFfW6aS4guwTFFQX78eS kCbw== MIME-Version: 1.0 X-Received: by 10.152.47.97 with SMTP id c1mr358761lan.6.1364975137917; Wed, 03 Apr 2013 00:45:37 -0700 (PDT) Received: by 10.112.81.198 with HTTP; Wed, 3 Apr 2013 00:45:37 -0700 (PDT) X-Originating-IP: [84.112.19.176] In-Reply-To: <3D6C3B4F-0633-4F18-BF7C-B57B40389E2A@gmail.com> References: <3D6C3B4F-0633-4F18-BF7C-B57B40389E2A@gmail.com> Date: Wed, 3 Apr 2013 09:45:37 +0200 Message-ID: Subject: Re: [ANNOUNCE] Apache CouchDB 1.2.2 has been released From: Dave Cottlehuber To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec554025a39230604d9700a26 X-Gm-Message-State: ALoCoQlQa/sdaqrqitvDOL3FsJY09Hs/yopwld7uoao1K0hK9SoZlDVmxzCx1UA9RiZ/PUUbND3x X-Virus-Checked: Checked by ClamAV on apache.org --bcaec554025a39230604d9700a26 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Andrew, What are the features / issues you'd like to see taken care of? A+ Dave On 3 April 2013 04:52, Andrew Melo wrote: > Hi Noah > > On Apr 2, 2013, at 21:45, Noah Slater wrote: > > > Nestor, > > > > Nope. But work on the BigCouch merge is active at the moment. Our 1.3.0 > > feature release should be done next week or so. And then in three month= s > we > > should see a 2.0.0 with new APIs (as a stepping stone for BigCouch) or > > BigCouch itself. > > When the eventual couchdb/bigcouch merge happens, whose build chain come > on top: Bigcouch's rebar setup or couchdb's system? > > Thanks, > Andrew > > > > > > Hope this helps, > > > > > > On 3 April 2013 03:07, Nestor Urquiza wrote: > > > >> Great news. > >> > >> Question: Is BigCouch code integrated? I have been reading the plans t= o > >> include BigCouch additions inside the Apache CouchDB project. I am > >> interested more than anything in the elastic clustering capability whi= ch > >> should allow to go beyond a terabyte of data stored managed by > "commodity > >> machines" instead of a big server. > >> > >> We have built our Document Management System around couchdb and this i= s > a > >> needed functionality. > >> > >> Thanks! > >> - Nestor > >> > >> On Tue, Apr 2, 2013 at 2:31 PM, Lance Carlson >>> wrote: > >> > >>> This is awesome! > >>> > >>> > >>> On Tue, Apr 2, 2013 at 1:58 PM, Noah Slater > wrote: > >>> > >>>> Dear community, > >>>> > >>>> Apache CouchDB 1.2.2 has been released and is available for download= . > >>>> > >>>> CouchDB is a database that completely embraces the web. Store your > data > >>>> with JSON documents. Access your documents with your web browser, vi= a > >>> HTTP. > >>>> Query, combine, and transform your documents with JavaScript. CouchD= B > >>> works > >>>> well with modern web and mobile apps. You can even serve web apps > >>> directly > >>>> out of CouchDB. And you can distribute your data, or your apps, > >>> efficiently > >>>> using CouchDB=92s incremental replication. CouchDB supports > master-master > >>>> setups with automatic conflict detection. > >>>> > >>>> Grab your copy here: > >>>> > >>>> http://couchdb.apache.org/ > >>>> > >>>> Pre-built packages for Windows and OS X are available. > >>>> > >>>> This is a bugfix release > >>>> > >>>> These release notes are based on the CHANGES file. > >>>> > >>>> HTTP Interface > >>>> > >>>> * Reset rewrite counter on new request, avoiding unnecessary > >> request > >>>> failures due to bogus rewrite limit reports. > >>>> > >>>> Build System > >>>> > >>>> * Fixed issue in couchdb script where stopped status returns > >> before > >>>> process exits. > >>>> > >>>> Thanks, > >>>> > >>>> -- > >>>> NS > > > > > > > > -- > > NS > --bcaec554025a39230604d9700a26--