Well, I think the standard disclaimer applies here: The trunk is not
guaranteed to be stable (but, hey, what really is, right?). Releases
are meant to be production ready to the best of our knowledge at
the time.
That being said, we do make efforts to keep the trunk stable. I
guess
-Original Message-
From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 9:27 AM
To: java-user@lucene.apache.org
Subject: Re: Is Lucene Java trunk still stable for production code?
Well, I think the standard disclaimer applies here: The trunk is not
guaranteed
[mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 9:27 AM
To: java-user@lucene.apache.org
Subject: Re: Is Lucene Java trunk still stable for production code?
Well, I think the standard disclaimer applies here: The trunk is not
guaranteed to be stable (but, hey, what really is, right
An index created with a formal version (major or minor), would be
readable
(and hence upgradable) by a later version.
In fact this is not guaranteed for every later version - only for those
up to one major step ahead. The Wiki's statement is very accurate here:
File formats are
-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 15, 2007 1:44 PM
To: java-user@lucene.apache.org
Cc: java-dev@lucene.apache.org
Subject: RE: Is Lucene Java trunk still stable for production code?
: Thanks for your insight, it matches my thoughts
: Thanks for your insight, it matches my thoughts. The only reason I'm
: wondering is because the latest change in the lucene_2_1 branch is 4
: weeks old. So either no bugs were found since then (yeah!) or the bugs
: gets fixed in the trunk...
The general policy that Doug has encouraged in teh
Hello Dear Lucene Users!
Back in the old days (well, last year) the lucene/java/trunk subversion
path was always stable enough for everyone to use into production code.
Now, with the 2.0/2.1/2.2 braches, is it still the case?
In December, I 'ported' my app to use the lucene 2.0 release.
