In the 3.0's backwards info! In 2.9.1 all stays as usual. I was a little bit confused this morning, because I have seen no relation between 2.9.1 and compress removal. It was under discussion, that we may need an update of 2.9, if we add new APIs to check for compressed fields or something similar. As 2.9.1 is not changed, nothing to do here and we can release.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Michael McCandless [mailto:luc...@mikemccandless.com] > Sent: Monday, October 26, 2009 11:00 AM > To: java-dev@lucene.apache.org > Subject: Re: 2.9.1 > > On Mon, Oct 26, 2009 at 1:21 AM, Michael Busch <busch...@gmail.com> wrote: > > Yeah, if everyone else is okay with the one-time performance hit during > > merge (details in LUCENE-1960), then I'm also +1 for cutting 2.9.1 > tomorrow! > > I think this is acceptable, but we should call it out clearly in the > "changes to back compat" section. > > Mike > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
