Michael Baessler wrote:
Hi,
I see Marshall has fixed the RAT issues reported by Thilo and the JIRA
bug tracking system says that we have no open issues to fix for uimaj
2.2.
So it seems that we are ready to build the hopefully latest release
candidate level.
+1
But what do we do with all the issues that hang around in the
"resolved" state. I think the assignee of the defect should verify the
resolved issue for the releases
2.1 and 2.2 before we build the next level.
+1
I don't think that we need a new level to resolve these issues, or I'm
wrong here?
I agree. The things in the resolved state should be changed to close
state (unless the person doing the change has an issue, of course).
I went thru the resolved / not closed, and for many where I knew the
situation, changed them to closed.
I know Eddie will try and finish up some doc changes today, also.
And we still have some open test cases... I can do some more testing
tomorrow, but I cannot do all. So please add you name to the tests
that you can look at.
When I took a look, the only open tests were the "migration" tools, and
testing the examples - some of which is done. (I also tested the SOAP
example - I'll add that.)
So I think we're good to go, once doc updates are in, and that includes
perhaps redoing the readme stuff for what's changed to capture the
additional Jira items relevant to the 2.2 release.
My plan was to build the uimaj-2.2.0-RC2 when all the tests are
executed and all the defects are verified. So that we can just need to
do a simple regression test
on this level. Does this sound good to you?
+1
-Marshall
