Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 48647 invoked from network); 15 Feb 2011 19:08:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Feb 2011 19:08:00 -0000 Received: (qmail 79333 invoked by uid 500); 15 Feb 2011 19:07:59 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 79229 invoked by uid 500); 15 Feb 2011 19:07:56 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 79222 invoked by uid 99); 15 Feb 2011 19:07:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 19:07:55 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rcmuir@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bw0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 19:07:47 +0000 Received: by bwz8 with SMTP id 8so768745bwz.35 for ; Tue, 15 Feb 2011 11:07:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type:content-transfer-encoding; bh=4h7DOmEo32wSFJEIw56c+J5mAxnwj3/4SlqKEdPz6zA=; b=R6ihYwFh3c/0jxxCa4dQPQXq/WifEoso73Nh6BfRKhwL43yVAbulQEWdS8Ui0kaEui tqsk7bFG6RMs3YkTENtf6NGJ2+2f7HspefXCoMCISRoc1uSa/3PRtuV2iiQzsGgylB3l OJrXpdnVrBoByoec8kbNtTJpWkFli7eLcZ9is= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=v6bDGrq6Bkdu70rmZa7dwAqQ6Y2nuqHirUG2PCjK8JANVzaHUL9jgm7PmA8d+mjf+X NFOdqhNtlx2Xa6SonX9S+VmeSnQyZY3/DVRmvgKU6vWaTy4wuJDxJP5Y9LSviRgvyLOK VUWgDXBTw6Ky+cvvUqDomhNBwzOvvm58hlbbU= Received: by 10.204.82.96 with SMTP id a32mr7358465bkl.179.1297796847297; Tue, 15 Feb 2011 11:07:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.101.5 with HTTP; Tue, 15 Feb 2011 11:07:07 -0800 (PST) In-Reply-To: References: <4D5AA1E7.9080801@gmail.com> <4D5ABF4A.507@gmail.com> From: Robert Muir Date: Tue, 15 Feb 2011 14:07:07 -0500 Message-ID: Subject: Re: Release 3.2 (was Re: Please mark distributed date faceting for 3.1) To: dev@lucene.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Feb 15, 2011 at 1:33 PM, Mark Miller wrote: >> >> It appears to me, that the effort to commit the contributions are minima= l, and that in this case the true cost is that of doing the release. > > Heh. I think looks can be deceiving sometimes. I'm not sure I'm willing t= o hold the responsibility of those commits right now. If someone else is, t= hat's great ... but I don't find them minimal enough for my taste I suppose= ;) Depends on what areas you feel comfortable with I guess. > Right, this is why some features with functional patches are sitting targeted at 3.2 instead of 3.1. Is it possible that we could put distributed date faceting (SOLR-1709), better cjk handling out of box (LUCENE-2906), and a better default merge policy (LUCENE-854) all in 3.1 right now? sure it is. But is this the best decision... I don't think it is. I think as far as 3.1 goes we already have a great set of features that have baked for some time, including some rather serious performance improvements (Mike and I have done some benchmarking against 3.0)... and its already going to be a more challenging release since its the first one since we merged lucene and solr. For these newer features, its not that we are lazy... its that sometimes you want more tests, want things to "bake" for a while with hudson's random testing, perhaps want some reviews/second pairs of eyes on the code, or maybe even just some more time to think about the change before committing to it. When we commit it and release it, we are signing up for some degree of support in the future. Also, personally I think its better to put out a good release with solid code and a few less features, than a more buggy release that has a couple of extra features. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org