Re: 2.2 release

[Thilo Goetz <tw...@gmx.de>]

Hi all,

according to our test plan (http://cwiki.apache.org/UIMA/testplan22.html),
we have entered testing for our 2.2 release.  We currently have the
following issues tagged as "fix for 2.2" in Jira:

UIMA-387 XMI Serializer can write invalid control characters   	
UIMA-219 Clean up XCASSerializer code to remove what's left of Sofa mapping support 	
UIMA-258 improve names of the UIMA documentation PDF files
UIMA-328 CDE - handle case of searching for impl Java class, but the project is not a Java project
UIMA-307 Fix CVD screenshots

I think 387 we agreed should be done for this release.  I'll try to
get to it tomorrow.  307 is documentation, I'll work on that during
the test phase.  However, it doesn't affect the code and so there's
no problem with that.

What about the others?  If we want to fix them for 2.2, we should do
so asap.  Opinions?

Please take a look at the test plan, if you haven't done so already.
There's a table with all the issues we wanted to fix for 2.2.  You
can add the documentation status of those issues there.  Maybe for
the next release, we could configure our Jira to have a column for
that?  It might be easier to track this all in one place.  Thoughts?

I looked over the rest of the open issues, those that are not
specifically targeted at 2.2.  There was nothing there that struck
me as absolutely needing to go into 2.2.  Anybody disagree?

Let me know what you think.

--Thilo

Re: 2.2 release

[Marshall Schor <ms...@schor.com>]

I suggest::

  258 - remove "fixed in 2.2"; wait until someone feels this is 
important enough
  328 - remove "fixed in 2.2"; wait until someone feels this is 
important enough

-Marshall

Thilo Goetz wrote:
> Hi all,
>
> according to our test plan (http://cwiki.apache.org/UIMA/testplan22.html),
> we have entered testing for our 2.2 release.  We currently have the
> following issues tagged as "fix for 2.2" in Jira:
>
> UIMA-387 XMI Serializer can write invalid control characters   	
> UIMA-219 Clean up XCASSerializer code to remove what's left of Sofa mapping support 	
> UIMA-258 improve names of the UIMA documentation PDF files
> UIMA-328 CDE - handle case of searching for impl Java class, but the project is not a Java project
> UIMA-307 Fix CVD screenshots
>
> I think 387 we agreed should be done for this release.  I'll try to
> get to it tomorrow.  307 is documentation, I'll work on that during
> the test phase.  However, it doesn't affect the code and so there's
> no problem with that.
>
> What about the others?  If we want to fix them for 2.2, we should do
> so asap.  Opinions?
>
> Please take a look at the test plan, if you haven't done so already.
> There's a table with all the issues we wanted to fix for 2.2.  You
> can add the documentation status of those issues there.  Maybe for
> the next release, we could configure our Jira to have a column for
> that?  It might be easier to track this all in one place.  Thoughts?
>
> I looked over the rest of the open issues, those that are not
> specifically targeted at 2.2.  There was nothing there that struck
> me as absolutely needing to go into 2.2.  Anybody disagree?
>
> Let me know what you think.
>
> --Thilo
>
>
>
>
>   

Re: 2.2 release

[Adam Lally <al...@alum.rpi.edu>]

On 6/26/07, Thilo Goetz <tw...@gmx.de> wrote:
> Hi all,
>
> according to our test plan (http://cwiki.apache.org/UIMA/testplan22.html),
> we have entered testing for our 2.2 release.  We currently have the
> following issues tagged as "fix for 2.2" in Jira:
>
> UIMA-387 XMI Serializer can write invalid control characters
> UIMA-219 Clean up XCASSerializer code to remove what's left of Sofa mapping support
> UIMA-258 improve names of the UIMA documentation PDF files
> UIMA-328 CDE - handle case of searching for impl Java class, but the project is not a Java project
> UIMA-307 Fix CVD screenshots
>

UIMA-219 is just code cleanup and isn't critical to get done for this release.

-Adam

Re: 2.2 release

[Adam Lally <al...@alum.rpi.edu>]

On 6/26/07, Thilo Goetz <tw...@gmx.de> wrote:
> Please take a look at the test plan, if you haven't done so already.
> There's a table with all the issues we wanted to fix for 2.2.  You
> can add the documentation status of those issues there.  Maybe for
> the next release, we could configure our Jira to have a column for
> that?  It might be easier to track this all in one place.  Thoughts?
>

I took care of the documentation for the issues assigned to me and
updated the status approprately.

I also added my name under the test scenarios that I plan to do.  I
have the test cases set up for these so it makes sense that I continue
to do them.

-Adam