Yeah it makes sense to keep it for convenience if we're removing it
from analyzers. So the proposal is:
* Keep Version around for convenience
* Remove its usage from non-analyzers code that wasn't released yet
(like IndexWriterConfig)
* Remove all pre-4.0 values from the trunk's version of Version
* Cancel 2305 and introduce it "on demand"

Shai

On Tuesday, May 4, 2010, Uwe Schindler <[email protected]> wrote:
> I would like to keep Version, as this is not related to backwards 
> compatibility in the sense. I cannot take care on the discussion (vacation), 
> I just want to tell my opinion, which is also used for any future voting I 
> cannot attend.
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: [email protected]
>
>> -----Original Message-----
>> From: Shai Erera [mailto:[email protected]]
>> Sent: Tuesday, May 04, 2010 7:39 PM
>> To: [email protected]
>> Subject: What is the future of Version?
>>
>> Hi
>>
>> So what did we agree on the future of Version? Do we remove it
>> entirely starting w/ 4.0? For analyzers it'd make sense b/c we say
>> that you can use a specific analyzers package version to get the
>> desired behavior. Since Version is mostly used in analyzers - do we
>> want to remove it entirely in 4.0?
>>
>> I've opened this issue
>> https://issues.apache.org/jira/browse/LUCENE-2305 and the decision
>> about Version will affect it.
>>
>> If we want to keep Version around, but in limited or "on demand" use,
>> then I think in trunk we should only have 4.x versions, w/o any priror
>> ones?
>>
>> Shai
>>
>> ---------------------------------------------------------------------
>> 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]
>
>

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

Reply via email to