Return-Path: Delivered-To: apmail-incubator-couchdb-dev-archive@locus.apache.org Received: (qmail 32828 invoked from network); 2 Dec 2008 19:39:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Dec 2008 19:39:16 -0000 Received: (qmail 57496 invoked by uid 500); 2 Dec 2008 19:39:27 -0000 Delivered-To: apmail-incubator-couchdb-dev-archive@incubator.apache.org Received: (qmail 57217 invoked by uid 500); 2 Dec 2008 19:39:27 -0000 Mailing-List: contact couchdb-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-dev@incubator.apache.org Delivered-To: mailing list couchdb-dev@incubator.apache.org Received: (qmail 57203 invoked by uid 99); 2 Dec 2008 19:39:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2008 11:39:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jchris@gmail.com designates 66.249.90.177 as permitted sender) Received: from [66.249.90.177] (HELO ik-out-1112.google.com) (66.249.90.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2008 19:37:56 +0000 Received: by ik-out-1112.google.com with SMTP id b35so2679161ika.4 for ; Tue, 02 Dec 2008 11:38:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=/Zh650O+xS33rFdG+qd0uob9L3Nep1L81Ii51LGiIxU=; b=vfCUxfa5nMBI2fnneyl4SuxwXBr7oPdu/dzqXQTBBuRYZhaKweMWQrSuVAIz4YDINj yaAlR+B/mPVMqCDWm9+o7pNLryVh+bqcex9fg/naKBJfI1vigEYHK4XZMLGYz8+nt0rD AeQ5ZqoTlfpTXPXC+btGSTB8G75XLnQdiSNcQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=aEfZ6C5C715dZuWPuakbhBlqphxfCUdIGaTLkVZTAiwf8Nr5F851RabKDgIsOYZ0Qd bgkKdYF2PEd1aUmJTEjMgRaMSVZcWJTrHqUF5Jib8wYwKHH177WXz7GLBw+iFue0ASAN JJl6tuvXXmvaeCgaateHurrkJj+K/EnodvMGw= Received: by 10.210.91.7 with SMTP id o7mr9154114ebb.16.1228246713149; Tue, 02 Dec 2008 11:38:33 -0800 (PST) Received: by 10.210.121.12 with HTTP; Tue, 2 Dec 2008 11:38:33 -0800 (PST) Message-ID: Date: Tue, 2 Dec 2008 11:38:33 -0800 From: "Chris Anderson" Sender: jchris@gmail.com To: couchdb-dev@incubator.apache.org Subject: Re: 0.9.0 Release In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 10847897021f697e X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Dec 2, 2008 at 11:29 AM, Damien Katz wrote: > I think we are just about ready for a 0.9.0 release and will be feature > complete enough to be considered Beta. Woo hoo! > > Two things I'd like before we release 0.9.0 is some replication testing of > the new security stuff and to finally change "count" to "limit" in view > query string arguments. count -> limit sounds simple enough. Perhaps if you wrote up in English what the replication security requirements are, someone else could add the tests. > > Also, some people have complaints about the programmatic interfaces for > map/reduce/rereduce functionality. If anyone wants to change these, or any > other major aspects of CouchDB interfaces, now is the time. It only gets > harder as we move forward. I'll say that I'm quite happy with the reduce/rereduce API as it currently stands. However, I'd like to make sure that there is room for some stock Erlang reduce functions to be available without a Javascript function definition. For starters reduce=row_count and reduce=sum would both be handy for a lot of applications, and implementing them as Erlang would mean that group=true queries would be fast. I think these features can be added in the future without breaking compatibility with existing libraries, so they don't need to happen now, but I wanted to bring it up in case there's something I'm not seeing. -- Chris Anderson http://jchris.mfdz.com