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:[email protected]] > Sent: Wednesday, April 24, 2013 3:43 PM > To: '[email protected]' > 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 >
