Mailing-List: contact general-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of yseeley@gmail.com designates
 74.125.82.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=mTtO9Hwcny5bYVAsUUkl7xaWv0E7pzgztbosW84KOnv+BcPZbHxQ1rydazs2BibWRX
         LMpOTKvPl/SNYoju2CG9tVUu1FNKRmcBvDY+hg1KGUkw+u8/oa0pA/RqxsqUhERWzED4
         ruM0mT4bFPMg9ujKej+kLd7XB2LG9hBiQsCvQ=
MIME-Version: 1.0
Sender: yseeley@gmail.com
In-Reply-To: 
 <alpine.OSX.2.01.1003041104580.89055@dhcp-wired-097.corp.631h.metaweb.com>
References: <c68e39171003031442i222fa450r16a4b38b21fc01f1@mail.gmail.com>
	 <004201cabb6a$f6698b40$e33ca1c0$@de>
	 <9ac0c6aa1003040227x5f7fe46es20aee42ce6ee895@mail.gmail.com>
	 <000601cabb88$964e2310$c2ea6930$@de>
	 <9ac0c6aa1003040540y41333d16ua957afa5f40363b4@mail.gmail.com>
	 <alpine.OSX.2.01.1003040849070.88961@yuzu.local>
	 <4B8FEFCF.2040807@gmail.com>
	 <3b5f72031003041048m65ee268ei8274fa4f3f06eee@mail.gmail.com>
	 <4B90027C.2090405@gmail.com>
	 <alpine.OSX.2.01.1003041104580.89055@dhcp-wired-097.corp.631h.metaweb.com>
Date: Thu, 4 Mar 2010 15:22:48 -0500
Message-ID: <c68e39171003041222x3ed03e4dl56415e710c96ef9b@mail.gmail.com>
Subject: Re: [VOTE] merge lucene/solr development
From: Yonik Seeley <yonik@apache.org>
To: general@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1

As far as releases - I'm not sure Lucene has released major versions
appreciably faster than Solr.  Lucene released many more bugfix
releases... but those are orders of magnitude easier - not an issue.

It is precisely the intent, goals, and commitments that matter to me.
A single development team.
I'm not sweating the small stuff - it will be worked out.  The
*intent* to try and develop and release together is what's important.

If we merge, and Solr's not on Lucene's trunk yet, and Lucene is close
to a release - of course it makes sense for Lucene to go ahead and
release.  It's all these things we *don't* have to specify because
we'll use our heads and not try to practice contract law ;-)
That's even true inside Solr itself - when it was felt that some
components weren't quite ready for "prime time", they didn't make it
into the release.

-Yonik