You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by Digy <di...@gmail.com> on 2011/03/02 23:41:00 UTC
RE: [Lucene.Net] [jira] Assigned: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
Hi Scott,
What is the meaning of this assignment? Is it like "Don't touch this issue I am working on it"?
Or can I work on it? But as I said before, I would prefer to work on diffs instead of issues.
DIGY
-----Original Message-----
From: Scott Lombard (JIRA) [mailto:jira@apache.org]
Sent: Thursday, February 24, 2011 7:03 AM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] [jira] Assigned: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
[ https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Lombard reassigned LUCENENET-399:
---------------------------------------
Assignee: Scott Lombard
> Port changes from Java Lucene 2.9.3 and 2.9.4 releases
> ------------------------------------------------------
>
> Key: LUCENENET-399
> URL: https://issues.apache.org/jira/browse/LUCENENET-399
> Project: Lucene.Net
> Issue Type: Task
> Components: Lucene.Net Core, Lucene.Net Test
> Reporter: Troy Howard
> Assignee: Scott Lombard
> Fix For: Lucene.Net 2.9.4
>
>
> Port changes from Java Lucene 2.9.3 and 2.9.4 releases.
> The Lucene.Net 2.9.4 release will roll up the changes from both of those releases into one.
> Unit tests should be added or updated to reflect the changes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Lucene.Net] [jira] Assigned: (LUCENENET-399) Port changes from
Java Lucene 2.9.3 and 2.9.4 releases
Posted by Scott Lombard <sl...@theta.net>.
Digy,
My assignment is just saying that I will take the lead in seeing that
the changes get ported. Feel free to work on any changes you would
like. I took the approach of reviewing the diffs for each java issue
making a commit for each issue I ported. That will give the ability
to trace changes back to specific issues. It will take more time than
a port between 2.9.2 and 2.9.4 using a single diff, but give the more
details in the svn if a problem develops.
I have been on vacation this week so I have only been checking email.
I will be back home on Friday and start working ports then.
Scott
On 3/2/11, Digy <di...@gmail.com> wrote:
> Hi Scott,
>
> What is the meaning of this assignment? Is it like "Don't touch this issue I
> am working on it"?
> Or can I work on it? But as I said before, I would prefer to work on diffs
> instead of issues.
>
> DIGY
>
>
> -----Original Message-----
> From: Scott Lombard (JIRA) [mailto:jira@apache.org]
> Sent: Thursday, February 24, 2011 7:03 AM
> To: lucene-net-dev@lucene.apache.org
> Subject: [Lucene.Net] [jira] Assigned: (LUCENENET-399) Port changes from
> Java Lucene 2.9.3 and 2.9.4 releases
>
>
> [
> https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Scott Lombard reassigned LUCENENET-399:
> ---------------------------------------
>
> Assignee: Scott Lombard
>
>> Port changes from Java Lucene 2.9.3 and 2.9.4 releases
>> ------------------------------------------------------
>>
>> Key: LUCENENET-399
>> URL: https://issues.apache.org/jira/browse/LUCENENET-399
>> Project: Lucene.Net
>> Issue Type: Task
>> Components: Lucene.Net Core, Lucene.Net Test
>> Reporter: Troy Howard
>> Assignee: Scott Lombard
>> Fix For: Lucene.Net 2.9.4
>>
>>
>> Port changes from Java Lucene 2.9.3 and 2.9.4 releases.
>> The Lucene.Net 2.9.4 release will roll up the changes from both of those
>> releases into one.
>> Unit tests should be added or updated to reflect the changes.
>
> --
> This message is automatically generated by JIRA.
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>