et atm.
>> The code should be in compliance with 3.0.3. We might want to do some spot
>> checking various parts of the code. I'm not sure about the tests. Also, we
>> should probably run some code coverage tools to see how much coverage we
>> have.
>> ~P
>&g
>> On 2012-06-14 17:58, Prescott Nasser wrote:
>>
>>> I'm going to try and review some of them - looking at the 3.5 ticket
>>> atm. The code should be in compliance with 3.0.3. We might want to do some
>>> spot checking various parts of the code. I'm not
Also, we
>> should probably run some code coverage tools to see how much coverage we
>> have.
>> ~P
>>
>>> Date: Thu, 14 Jun 2012 18:37:12 +0300
>>> Subject: Re: Releasing 3.0.3
>>> From: ita...@code972.com
>>> To: lucene-net-dev@lucene.
Thanks,
Christopher
On Thu, Jun 14, 2012 at 8:58 AM, Prescott Nasser wrote:
>
> I'm going to try and review some of them - looking at the 3.5 ticket atm.
> The code should be in compliance with 3.0.3. We might want to do some spot
> checking various parts of the code. I'm not
code should be in compliance with 3.0.3. We might want to do some spot checking
various parts of the code. I'm not sure about the tests. Also, we should
probably run some code coverage tools to see how much coverage we have.
~P
Date: Thu, 14 Jun 2012 18:37:12 +0300
Subject: Re: Releasin
h coverage we have.
~P
> Date: Thu, 14 Jun 2012 18:37:12 +0300
> Subject: Re: Releasing 3.0.3
> From: ita...@code972.com
> To: lucene-net-dev@lucene.apache.org
>
> Ok, and is the code in 100% compliance with the 3.0.3 Java code?
>
> I'll be spending some time on fixin
Ok, and is the code in 100% compliance with the 3.0.3 Java code?
I'll be spending some time on fixing the index corruption issue, and it is
probably best for Chris to wrap up the work he has started
Anyone else on board to close some tickets?
On Thu, Jun 14, 2012 at 6:19 PM, Prescott Nasser wrot
Agreed -
JIRA for 3.0.3
https://issues.apache.org/jira/browse/LUCENENET/fixforversion/12316215#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
We should evaluate all of these - fix them, mark as won't fix, or move them to
another release version. I think the biggest h
