I think the problem right now isn't whether we are going to have 1.5 code or not. We will eventually have to have 1.5 code anyways. But we need a sound plan that will make the transition easy. I believe the transition from 1.4 to 1.5 is not an over night thing.
Secondly can we specifically find places where some people _will_ contribute code immediately if it's 1.5 is accepted? Like what I have suggested before, why not have contribution modules that act as a transition into 1.5 code? Much like what other framework has a "tiger" module. This module may have say, a 1.5 compatible layer on top of 1.4 core, or other components of lucene that was made to be extensible, e.g. 1.5 version of QueryParser, Directory, etc. ray, On 6/17/06, Paul Elschot <[EMAIL PROTECTED]> wrote:
On Saturday 17 June 2006 01:33, markharw00d wrote: > > That's a long-winded way of saying "-1" unless I hear of any arguments > which are based on something much more substantial than "1.5 makes > coding easier". As for coding convenience from 1.4: last time I had a look there was not a single assert statement in the core code, so I don't think coding convenience is a good argument to move to 1.5 already now. Regards, Paul Elschot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
