Return-Path: Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org Received: (qmail 90332 invoked from network); 8 Jun 2006 23:20:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Jun 2006 23:20:16 -0000 Received: (qmail 16698 invoked by uid 500); 8 Jun 2006 23:20:16 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 16584 invoked by uid 500); 8 Jun 2006 23:20:15 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 16566 invoked by uid 99); 8 Jun 2006 23:20:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 16:20:15 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of yseeley@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 16:20:14 -0700 Received: by py-out-1112.google.com with SMTP id 57so666011pya for ; Thu, 08 Jun 2006 16:19:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VDI8oJIWKKgW9HeQoEqPeMgjkHqW5+W0loYFaNr3u3xHwLoCBGYkDqc5k5gfnSOhHZ0j4ulKoCVh3vIBJy76TGrPQ9w3MLqg5/+t9USYAxKINilfR12MpH+aqYcPY7NZ+C8zjeTgugBbkrE/PblX4FVWLZHBKm7do3zqmTk+2Fw= Received: by 10.35.88.18 with SMTP id q18mr3111192pyl; Thu, 08 Jun 2006 16:19:54 -0700 (PDT) Received: by 10.35.129.12 with HTTP; Thu, 8 Jun 2006 16:19:54 -0700 (PDT) Message-ID: Date: Thu, 8 Jun 2006 19:19:54 -0400 From: "Yonik Seeley" To: solr-user@lucene.apache.org Subject: Re: Lucene versioning policy In-Reply-To: <3d2ce8cb0606081611t7f6a81baudce913810af2d2d6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3d2ce8cb0606081611t7f6a81baudce913810af2d2d6@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 6/8/06, Mike Klaas wrote: > I was curious as to policy regarding being current with the lucene > codebase. Does solr use the lastest stable release? bleeding edge > (trunk?) Occasional manual svn import? An occasional SVN import based on need (same as hadoop/nutch as far as I can see). Lucene releases are to far and few between to always go with a "stable" version. Solr is stocked with Lucene committers, so we know what's is going in. If we find a Lucene problem, I'd rather make a fix directly to Lucene and use it rather than attempting to work around it. Also, as a Lucene committer, I also like making sure the current version is stable. > Also, are there any plans to split solr into a release/development mode? Definitely. (just no dates have been set yet) > I'd really like to use solr in a commercial setting, but having nothing but > nightly builds available makes me uneasy. Anything you develop would need to be QA'd for a commercial setting anyway. Perhaps you could pick the latest nightly build, make sure it works for your application, and stick with it a while :-) -Yonik http://incubator.apache.org/solr Solr, the open-source Lucene search server