lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Digy" <>
Subject RE: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2
Date Thu, 19 Mar 2009 17:38:27 GMT
I am not sure about LUCENENET-173 patch. Some mono users may benefit of it but some users are
getting errors while using it. Besides that it is not a complete builder for .NET applications.
It doesn't handle embedded resources, conditional compilations etc. And monodevelop makes
all these quite well.


-----Original Message-----
From: George Aroush (JIRA) [] 
Sent: Thursday, March 19, 2009 3:22 AM
Subject: [jira] Commented: (LUCENENET-164) upgrade from version 2.3.1. to 2.3.2


George Aroush commented on LUCENENET-164:


I have no objection.  I'm 1/2 way done reviewing the patch for 2.3.2, and expect to finish
it over the weekend; worse case we can make changes to the trunk after you created a 2.3.1
tag.  If you need help on creating the tag, let me know.

Before you do so, please do the following in the trunk:

1) Resolve LUCENENET-173 in the current trunk (this is a good patch to have and carry over).

2) update \trunk\C#\src\HISTORY.txt and label it as "final".  E.g.:

        - Release:  Apache Lucene.Net.2.3.1 build 003 "final"

3) Check that all AssemblyInfo.cs files have the correct build number (in \trunk\C#\src\ only,
this is since we didn't touch anything in contrib)


-- George

> upgrade from version 2.3.1. to 2.3.2
> ------------------------------------
>                 Key: LUCENENET-164
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Improvement
>            Reporter: Doug Sale
>         Attachments: 2.3.2-Candidate.patch, LUCENENET-106 Patch for v2.3.2.patch, TestIndexModifier.patch
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> This issue is a placeholder for attaching a comprehensive patch upgrading the SVN HEAD
of Lucene.Net from 2.3.1 candidate to 2.3.2 candidate.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message