On Mon, Aug 10, 2009 at 9:12 PM, Grant Ingersollgsing...@apache.org wrote:
Or... and this is one crazy idea... maybe we should simply release 3.0
next, not removing any deprecated APIs until 3.1 or later. Ie,
normal software on having so many major changes would release an X.0
release; I
On Aug 10, 2009, at 3:06 PM, Michael Busch wrote:
I think we should change the backwards-compatibility policy as
proposed in LUCENE-1698 and remove some deprecated things (inlcuding
the old TokenStream API, maybe query parser) in 3.1, not 3.0.
Maybe. I'm not convinced yet that the
You didn't really comment on my proposal: I suggested to not remove the
old Token API and old queryparser in 3.0. Instead with 3.0 change the
bw-policy, so that we can remove deprecated things in minor releases
(e.g. 3.1 in this case).
I think your 2.5 proposal has drawbacks: if we release
On Aug 10, 2009, at 3:36 PM, Michael Busch wrote:
You didn't really comment on my proposal: I suggested to not remove
the old Token API and old queryparser in 3.0. Instead with 3.0
change the bw-policy, so that we can remove deprecated things in
minor releases (e.g. 3.1 in this case).
On 8/10/09 1:30 PM, Grant Ingersoll wrote:
I think your 2.5 proposal has drawbacks: if we release 2.5 now to
test the new major features in the field, then do you want to stop
adding new features to trunk until we release 2.9 to not have the
same situation then again? How long should this
On Tue, Aug 11, 2009 at 00:37, Michael Buschbusch...@gmail.com wrote:
On 8/10/09 1:30 PM, Grant Ingersoll wrote:
I think your 2.5 proposal has drawbacks: if we release 2.5 now to test
the new major features in the field, then do you want to stop adding new
features to trunk until we release
I do agree 2.9 has tons of changes: new analysis API, segment-based
searching/collection/sorting, new QP, etc.
One option might be to have a looong beta period for 2.9, and focus on
testing/docs?
Or... and this is one crazy idea... maybe we should simply release 3.0
next, not removing any
Does this mean we still move to Java 5 in 3.0? If so, +1 from me too.
On Tue, Aug 11, 2009 at 12:06 AM, Mark Miller markrmil...@gmail.com wrote:
Michael McCandless wrote:
Or... and this is one crazy idea... maybe we should simply release 3.0
next, not removing any deprecated APIs until 3.1
You'll sell your vote for pork? :)
If by some miracle we went with this, with so many back compat issues
with this update, I don't see why we wouldn't throw Java 1.5 in as well.
That just complicates things here though. I'd save that discussion.
Shai Erera wrote:
Does this mean we still move
On 8/10/09 2:05 PM, Michael McCandless wrote:
Or... and this is one crazy idea... maybe we should simply release 3.0
next, not removing any deprecated APIs until 3.1 or later. Ie,
normal software on having so many major changes would release an X.0
release; I agree the deprecation release is
On Aug 10, 2009, at 18:48, Michael Busch busch...@gmail.com wrote:
On 8/10/09 2:05 PM, Michael McCandless wrote:
Or... and this is one crazy idea... maybe we should simply release
3.0
next, not removing any deprecated APIs until 3.1 or later. Ie,
normal software on having so many major
11 matches
Mail list logo
