lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: lucene and solr trunk
Date Tue, 16 Mar 2010 22:42:51 GMT
Dev is now merged with Solr and Lucene -- that has already passed.  If
that will scare customers away, that's a risk we take -- the benefits
of merged dev outweigh that, in my opinion.

The incremental risk that the details of our svn URLs will scare
people away seems negligible.

And we can always change this up, later, if we decide to.

I think what's important now is a we pick something to un-block trunk
dev.  Sure people can keep working on the branch but I think it'd be
better if we get this simple "svn move" done so that we can get normal
dev going on a shared trunk again.

Mike

On Tue, Mar 16, 2010 at 5:28 PM, Jake Mannix <jake.mannix@gmail.com> wrote:
>
> On Tue, Mar 16, 2010 at 3:10 PM, Yonik Seeley <yseeley@gmail.com> wrote:
>>
>> On Tue, Mar 16, 2010 at 6:01 PM, Jake Mannix <jake.mannix@gmail.com>
>> wrote:
>> > I'm not concerned with casual downloaders.  I'm talking
>>
>> > about the companies and people who may or may not be
>>
>> > interested in making multi-million dollar decisions regarding
>>
>> > using or not using Lucene or Solr.
>>
>> Heh - multi-million dollar decisions after a quick glance at an SVN url?
>
> Clearly not.  But just as I think that making the development of
> both solr and lucene easier is a noble goal, I think that giving
> people the impression that by choosing to "go with Lucene"
> *means* they "go with Solr" as their end solution is not what
> we want to do.  There are some places where Solr is just not
> appropriate but Lucene may be.
> Will this impression be "caused" by a SVN directory url
> alone? Of course not.  Merging committer lists, locked
> releases, *and* a SVN url which shows this?  Yes, I
> think the kinds of VPs and CTO's I've talked to and
> tried to help decide whether to go with an open-source
> search solution could indeed start to get the feeling that
> there's really just one apache solution, the
> "Solr/Lucene solution".  And if they look into Solr and
> decide that this particular application is not for them,
> they may then not look deep enough to see whether
> doing a custom Lucene application *would be*.
>   -jake

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message