You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Masanz, James J." <Ma...@mayo.edu> on 2013/04/24 21:42:21 UTC

CTAKES-143 - dictionary lookup iterates inefficiently

Tim,  was an improvement equivalent to  "CTAKES-143 - dictionary lookup iterates inefficiently" put into trunk?  I see it's marked as resolved.

All,
I don't think we've discussed as a group how we'd like to handle the statuses on JIRA issues.
Should the person  marking an issue Resolved indicate the Fix Version if the resolution involved a code change.
Or does a release manager fill in the Fix Version when creating the release?

I see cTAKES-143 is not included in the releases notes for 3.0.0-incubating.
I want to make sure it gets included in the next release.

-- James



RE: CTAKES-143 - dictionary lookup iterates inefficiently

Posted by "Chen, Pei" <Pe...@childrens.harvard.edu>.
I normally mark items in Jira as:
1) Fixed once it's committed into trunk
2) Resolved when a release is cut
3) Closed after a version has been released and fix has been verified

> -----Original Message-----
> From: Masanz, James J. [mailto:Masanz.James@mayo.edu]
> Sent: Wednesday, April 24, 2013 3:43 PM
> To: 'dev@ctakes.apache.org'
> Subject: CTAKES-143 - dictionary lookup iterates inefficiently
> 
> Tim,  was an improvement equivalent to  "CTAKES-143 - dictionary lookup
> iterates inefficiently" put into trunk?  I see it's marked as resolved.
> 
> All,
> I don't think we've discussed as a group how we'd like to handle the statuses
> on JIRA issues.
> Should the person  marking an issue Resolved indicate the Fix Version if the
> resolution involved a code change.
> Or does a release manager fill in the Fix Version when creating the release?
> 
> I see cTAKES-143 is not included in the releases notes for 3.0.0-incubating.
> I want to make sure it gets included in the next release.
> 
> -- James
> 


Re: CTAKES-143 - dictionary lookup iterates inefficiently

Posted by Tim Miller <ti...@childrens.harvard.edu>.
Looks like I included it in this commit:

    r1442975 | tmill | 2013-02-06 09:15:47 -0500 (Wed, 06 Feb 2013) | 5
    lines

    Addresses ctakes-143. Adds interface method getSortedLookupTokens to
    allow/ensure optimal handling of sorted underlying types in
    dictionary lookup.
    Implemented changed versions of other classes implementing classes
    but did not test since they are not used in ctakes as far as I can tell.
    See discussion on ctakes-dev for further information
    (http://mail-archives.apache.org/mod_mbox/incubator-ctakes-dev/201302.mbox/%3C51102B9B.3000206%40childrens.harvard.edu%3E)

I don't know if it wasn't included or just not mentioned for the release.
Tim

On 04/24/2013 03:42 PM, Masanz, James J. wrote:
> Tim,  was an improvement equivalent to  "CTAKES-143 - dictionary lookup iterates inefficiently" put into trunk?  I see it's marked as resolved.
>
> All,
> I don't think we've discussed as a group how we'd like to handle the statuses on JIRA issues.
> Should the person  marking an issue Resolved indicate the Fix Version if the resolution involved a code change.
> Or does a release manager fill in the Fix Version when creating the release?
>
> I see cTAKES-143 is not included in the releases notes for 3.0.0-incubating.
> I want to make sure it gets included in the next release.
>
> -- James
>
>
>