I didn't know "release candidate" has so formal meaning. Let's name it
"mature version" for now.

DIGY.

-----Original Message-----
From: George Aroush [mailto:[EMAIL PROTECTED] 
Sent: Monday, November 17, 2008 4:18 AM
To: [email protected]
Subject: RE: Lucene.Net 2.3.1 Candidate

Hi DIGY,

Few more things are needed before the SVN trunk can be promoted to release
candidate, those are:

1) All AssemblyInfo.cs in /trunck/C#/src/ should have the same assembly
version.
2) /trunck/C#/src/HISTORY.txt file need to reflect what has been fixed, show
the build version and that this is a RC (release candidate) (change it to
"final" when it becomes a release)

After those changes, the community should start using the code off this
trunk and if there is no issue for, lets say a month, a vote for release
should be called.

One of the tests that I have always done before I nominate a build for RC is
verify that the index works with Java Lucene; you should take the time and
do some basic test on this area too.  Have the same index be modified by
Java Lucene and then by Lucene.Net.

Regards,

-- George


> -----Original Message-----
> From: Digy [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, November 16, 2008 10:03 AM
> To: [email protected]
> Subject: RE: Lucene.Net 2.3.1 Candidate
> 
> Hi All,
> 
>  
> 
> All waiting patches to make Nunit tests pass  
> (+LUCENENET-159) are applied. 
> 
> Release candidate for Lucene.Net.2.3.1 is in svn trunk now.
> 
>  
> 
> DIGY
> 
>  
> 
> From: Doug Sale [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 09, 2008 12:08 AM
> To: [email protected]
> Subject: Lucene.Net 2.3.1 Candidate
> 
>  
> 
> I believe we have a candidate for the Lucene.Net 2.3.1 
> release.  It diverges from the SVN HEAD by the list of patches below.
> 
> LUCENENET-135 SupportClass.patch
> LUCENENET-143 TestStressIndexing2.patch, FieldsReader.patch
> LUCENENET-145 DocumentsWriter.patch
> LUCENENET-146 SegmentTermPositionVector.
> 
> patch
> LUCENENET-151 MultiPhraseQuery.patch
> 
> LUCENENET-152 SegmentInfos.patch, FSDirectory.patch
> 
> LUCENENET-154 TestIndexWriterLockRelease.patch
> LUCENENET-155 SetUp.patch
> LUCENENET-157 GetFieldNames.patch
> LUCENENET-158 CheckHits.patch
> 
> I have attached a comprehensive patch to simplify things for 
> those of you who would like to try it out.
> 
> 1) Get the latest from SVN HEAD (currently revision 702987)
> 2) Apply Comprehensive.patch from the root directory.
> 
> - Doug
> 
> 

Reply via email to