Is Lucene Java trunk still stable for production code?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Is Lucene Java trunk still stable for production code?

Robichaud, Jean-Philippe-2
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.  Now, I
have another chance to upgrade the production code (this is not
happening every month!) so I would like to upgrade the lucene library
I'm using to take advantage of performance gains.  Should I just update
my svn image from lucene/java/trunk or should I take
lucene/java/branches/lucene_2_1

 

Thanks!

 

Jp

Reply | Threaded
Open this post in threaded view
|

Re: Is Lucene Java trunk still stable for production code?

Grant Ingersoll-2
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 the answer ultimately depends on your business needs.  If I  
were doing it, I would move to 2.1, but that's just me!

-Grant

On Mar 14, 2007, at 5:12 PM, Jean-Philippe Robichaud wrote:

> 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.  Now, I
> have another chance to upgrade the production code (this is not
> happening every month!) so I would like to upgrade the lucene library
> I'm using to take advantage of performance gains.  Should I just  
> update
> my svn image from lucene/java/trunk or should I take
> lucene/java/branches/lucene_2_1
>
>
>
> Thanks!
>
>
>
> Jp
>

--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org

Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ 
LuceneFAQ



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Is Lucene Java trunk still stable for production code?

Robichaud, Jean-Philippe-2
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...

I'll search JIRA and decides after!

Thanks!

Jp

-----Original Message-----
From: Grant Ingersoll [mailto:[hidden email]]
Sent: Thursday, March 15, 2007 9:27 AM
To: [hidden email]
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?).  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 the answer ultimately depends on your business needs.  If I  
were doing it, I would move to 2.1, but that's just me!

-Grant

On Mar 14, 2007, at 5:12 PM, Jean-Philippe Robichaud wrote:

> 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.  Now, I
> have another chance to upgrade the production code (this is not
> happening every month!) so I would like to upgrade the lucene library
> I'm using to take advantage of performance gains.  Should I just  
> update
> my svn image from lucene/java/trunk or should I take
> lucene/java/branches/lucene_2_1
>
>
>
> Thanks!
>
>
>
> Jp
>

--------------------------
Grant Ingersoll
Center for Natural Language Processing
http://www.cnlp.org

Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/ 
LuceneFAQ



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Is Lucene Java trunk still stable for production code?

Doron Cohen
A good reason for applications to only use formal versions (vs. trunk) is
backwards compatibility (see "BackwardsCompatibility" in Lucene Wiki).

An index created with a formal version (major or minor), would be readable
(and hence upgradable) by a later version. But for interim trunk states
this is not guaranteed. For example, version 2.2 will correctly open a 2.1
index, but it might fail to open an index created with (say) the current
trunk (in between 2.1 and 2.2).

Doron

"Jean-Philippe Robichaud" <[hidden email]> wrote on
15/03/2007 06:32:47:

> 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...
>
> I'll search JIRA and decides after!
>
> Thanks!
>
> Jp
>
> -----Original Message-----
> From: Grant Ingersoll [mailto:[hidden email]]
> Sent: Thursday, March 15, 2007 9:27 AM
> To: [hidden email]
> 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?).  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 the answer ultimately depends on your business needs.  If I
> were doing it, I would move to 2.1, but that's just me!
>
> -Grant
>
> On Mar 14, 2007, at 5:12 PM, Jean-Philippe Robichaud wrote:
>
> > 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.  Now, I
> > have another chance to upgrade the production code (this is not
> > happening every month!) so I would like to upgrade the lucene library
> > I'm using to take advantage of performance gains.  Should I just
> > update
> > my svn image from lucene/java/trunk or should I take
> > lucene/java/branches/lucene_2_1
> >
> >
> >
> > Thanks!
> >
> >
> >
> > Jp
> >
>
> --------------------------
> Grant Ingersoll
> Center for Natural Language Processing
> http://www.cnlp.org
>
> Read the Lucene Java FAQ at http://wiki.apache.org/jakarta-lucene/
> LuceneFAQ
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Is Lucene Java trunk still stable for production code?

Doron Cohen
> 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 back-compatible between major versions.  Version X.N
   should be able to read indexes generated by any version after and
   including version X-1.0, but may-or-may-not be able to read indexes
   generated by version X-2.N.



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Is Lucene Java trunk still stable for production code?

Chris Hostetter-3
In reply to this post by Robichaud, Jean-Philippe-2

: 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 past is to only commit
to the patch branch if/when a patch release is going to be made ... that
way there are less conflicts with merging and it's easier to understand
what exactly is going intothe patch release.

In general, i would suggest that the trunk no longer be considered
"stable" ... the current momentum is for more frequent releases, one
motivation for which is so people wanting "stable" builds don't feel
like they need to ues the trunk for the latest features,taking some burden
off commiters from needing to feel like every commit must be perfect
because users rely on the trunk being stable.

(or in short: we're moving more towards a *true* commit and review model)



-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Is Lucene Java trunk still stable for production code?

Robichaud, Jean-Philippe-2
That's really wonderful.  Everything gets cleaner now.

Thanks, I mean really Thanks, for all the hard work that goes in Lucene
code + Doc + Processes + Mailing list.  Lucene is really something I
refer other as "what (open source) software development should be".

I'll go with lucene_2_1 !

Jp

-----Original Message-----
From: Chris Hostetter [mailto:[hidden email]]
Sent: Thursday, March 15, 2007 1:44 PM
To: [hidden email]
Cc: [hidden email]
Subject: RE: Is Lucene Java trunk still stable for production code?


: 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 past is to only
commit
to the patch branch if/when a patch release is going to be made ... that
way there are less conflicts with merging and it's easier to understand
what exactly is going intothe patch release.

In general, i would suggest that the trunk no longer be considered
"stable" ... the current momentum is for more frequent releases, one
motivation for which is so people wanting "stable" builds don't feel
like they need to ues the trunk for the latest features,taking some
burden
off commiters from needing to feel like every commit must be perfect
because users rely on the trunk being stable.

(or in short: we're moving more towards a *true* commit and review
model)



-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]