Lucene versioning policy

[Mike Klaas <mi...@gmail.com>]

Hello,

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?

Also, are there any plans to split solr into a release/development mode?

I'd really like to use solr in a commercial setting, but having nothing but
nightly builds available makes me uneasy.

Thanks in advance,
-Mike

RE: Lucene versioning policy

[Darren Vengroff <ve...@gmail.com>]

Any update on possible graduation from the incubator?  Any chance it could
coincide with Hoss's presentation at ApacheCon?

-D

-----Original Message-----
From: Chris Hostetter [mailto:hossman_lucene@fucit.org] 
Sent: Thursday, June 08, 2006 11:48 PM
To: solr-user@lucene.apache.org
Subject: Re: Lucene versioning policy


: Also, are there any plans to split solr into a release/development mode?
:
: I'd really like to use solr in a commercial setting, but having nothing
but
: nightly builds available makes me uneasy.

I believe that as long as Solr is in the incubator, nightly builds are the
only releases we are allowed to have.  This is a side note in the
incubation policy about exiting incubation...

   Note: incubator projects are not permitted to issue an official
   Release. Test snapshots (however good the quality) and Release
   plans are OK.

...of course, there is some conflicting info higher up in the same doc
that suggests they are allowed, but they require jumping through some
hoops...

http://incubator.apache.org/incubation/Incubation_Policy.html#Releases


-Hoss

Re: Lucene versioning policy

[Chris Hostetter <ho...@fucit.org>]

: Also, are there any plans to split solr into a release/development mode?
:
: I'd really like to use solr in a commercial setting, but having nothing but
: nightly builds available makes me uneasy.

I believe that as long as Solr is in the incubator, nightly builds are the
only releases we are allowed to have.  This is a side note in the
incubation policy about exiting incubation...

   Note: incubator projects are not permitted to issue an official
   Release. Test snapshots (however good the quality) and Release
   plans are OK.

...of course, there is some conflicting info higher up in the same doc
that suggests they are allowed, but they require jumping through some
hoops...

http://incubator.apache.org/incubation/Incubation_Policy.html#Releases


-Hoss

Re: Lucene versioning policy

[Chris Hostetter <ho...@fucit.org>]

: http://svn.apache.org/viewvc/incubator/solr/trunk/CHANGES.txt
:
: But it is imperfect...  Perhaps an entry should be added when updating
: the Lucene version too.

+1 ... definitely.


-Hoss

Re: Lucene versioning policy

[Yonik Seeley <ys...@gmail.com>]

On 6/8/06, Mike Klaas <mi...@gmail.com> wrote:
> Even something as simple as 'tagging' a nightly build that contains
> major changes (with a brief changelog) would be helpful.  It would
> also be valuable from a project history perspective.

We try to record all non-trivial changes that can have an impact on
end users here:
http://svn.apache.org/viewvc/incubator/solr/trunk/CHANGES.txt

But it is imperfect...  Perhaps an entry should be added when updating
the Lucene version too.

-Yonik

Re: Lucene versioning policy

[Mike Klaas <mi...@gmail.com>]

On 6/8/06, Yonik Seeley <ys...@gmail.com> wrote:

> > 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 :-)

Thanks, Yonik.  That is what I have been doing so far, and it is fine
for now.  The difficulty is not knowing when important bugfixes occur,
major features added, etc., without closely watching svn activity.
Even something as simple as 'tagging' a nightly build that contains
major changes (with a brief changelog) would be helpful.  It would
also be valuable from a project history perspective.

Thanks again--I think solr is a phenomenal little product.
-Mike

Re: Lucene versioning policy

[Yonik Seeley <ys...@gmail.com>]

On 6/8/06, Mike Klaas <mi...@gmail.com> 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