You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Thilo Goetz <tw...@gmx.de> on 2007/05/25 10:07:42 UTC
2.2 release
Hi all,
how are we doing for our next release? I have a couple of minor things I want to
commit, but nothing major. I'd like to propose the following schedule:
6/1: feature freeze, start testing, make sure documentation is up to date
6/8: if no major bugs found, build release candidate and start vote
We have a couple of major items in this release that we need to test carefully:
- the new Pear runtime
- the JCas class loading improvements and CAS reorg
Anything else? Comments?
--Thilo
Re: 2.2 release
Posted by 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
Posted by 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
Posted by 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
Re: 2.2 release
Posted by 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
Posted by Thilo Goetz <tw...@gmx.de>.
Right, I missed that one because it's so recent. Working on it...
Marshall Schor wrote:
> Thilo Goetz wrote:
> Has any progress been made on UIMA-464 (a classcast exeption using an
> FSIterator returned by the AnnotationIndex.subiterator(AnnotationFS)?
>
> If this is a bug, I'd like to see it fixed for 2.2...
>
> -Marshall
Re: 2.2 release
Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
Has any progress been made on UIMA-464 (a classcast exeption using an
FSIterator returned by the AnnotationIndex.subiterator(AnnotationFS)?
If this is a bug, I'd like to see it fixed for 2.2...
-Marshall
Re: 2.2 release
Posted by Adam Lally <al...@alum.rpi.edu>.
We should collectively look through the list of JIRA issues that are
currently tagged as fix-for 2.2 and decided if we're going to fix them
or not for this release. For instance there's the one about control
characters in XML 1.0.
I do not think I will have very much time next week to devote to this.
-Adam
On 5/25/07, Thilo Goetz <tw...@gmx.de> wrote:
> Hi all,
>
> how are we doing for our next release? I have a couple of minor things I want to
> commit, but nothing major. I'd like to propose the following schedule:
>
> 6/1: feature freeze, start testing, make sure documentation is up to date
> 6/8: if no major bugs found, build release candidate and start vote
>
> We have a couple of major items in this release that we need to test carefully:
>
> - the new Pear runtime
> - the JCas class loading improvements and CAS reorg
>
> Anything else? Comments?
>
> --Thilo
>
>
>
>
Re: 2.2 release
Posted by Michael Baessler <mb...@michael-baessler.de>.
Thilo Goetz wrote:
> Marshall Schor wrote:
>
>> Thilo Goetz wrote:
>>
>>> Hi all,
>>>
>>> how are we doing for our next release?
>>>
>> It would be good if someone went through Jira and categorized the open
>> issues. A quick look shows 88 unresolved issues. I know we don't have
>> to do all of these for 2.2, but let's consider which one(s) to do. The
>> ones causing customer complaints we should consider doing :-)
>>
>> -Marshall
>>
>
> Sounds like people are pretty busy, and it might be better to take some
> extra time for finishing up coding/documentation for this release. So I
> propose to push back feature freeze to 6/8, a week from Friday. Is that
> agreeable with everybody?
Fine with me.
-- Michael
Re: 2.2 release
Posted by Adam Lally <al...@alum.rpi.edu>.
On 5/29/07, Thilo Goetz <tw...@gmx.de> wrote:
> Sounds like people are pretty busy, and it might be better to take some
> extra time for finishing up coding/documentation for this release. So I
> propose to push back feature freeze to 6/8, a week from Friday. Is that
> agreeable with everybody?
>
Agreed.
-Adam
Re: 2.2 release
Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Thilo Goetz wrote:
>> Hi all,
>>
>> how are we doing for our next release?
> It would be good if someone went through Jira and categorized the open
> issues. A quick look shows 88 unresolved issues. I know we don't have
> to do all of these for 2.2, but let's consider which one(s) to do. The
> ones causing customer complaints we should consider doing :-)
>
> -Marshall
Sounds like people are pretty busy, and it might be better to take some
extra time for finishing up coding/documentation for this release. So I
propose to push back feature freeze to 6/8, a week from Friday. Is that
agreeable with everybody?
--Thilo
Re: 2.2 release
Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
> Hi all,
>
> how are we doing for our next release?
It would be good if someone went through Jira and categorized the open
issues. A quick look shows 88 unresolved issues. I know we don't have
to do all of these for 2.2, but let's consider which one(s) to do. The
ones causing customer complaints we should consider doing :-)
-Marshall
RE: 2.2 release
Posted by Scott Songlin Piao <sc...@manchester.ac.uk>.
Will the version 2.2 work with Axis 2.2? If not, any plan to do it?
In the website manual of the version 2.1, it is said to support Apache Axis 1.1 or 1.3 only.
Scott
-----Original Message-----
From: Thilo Goetz [mailto:twgoetz@gmx.de]
Sent: 28 May 2007 16:15
To: uima-dev@incubator.apache.org
Subject: Re: 2.2 release
Marshall Schor wrote:
> Thilo Goetz wrote:
>> Hi all,
>>
>> how are we doing for our next release? I have a couple of minor
>> things I want to
>> commit, but nothing major. I'd like to propose the following schedule:
>>
>> 6/1: feature freeze, start testing, make sure documentation is up to date
>> 6/8: if no major bugs found, build release candidate and start vote
>>
>> We have a couple of major items in this release that we need to test
>> carefully:
>>
>> - the new Pear runtime
>> - the JCas class loading improvements and CAS reorg
>>
>> Anything else?
> Class loader switching :-) Shouldn't be too hard to do if I don't get
> swampped with other work next week.
> -Marshall
That's actually what I mean by "JCas class loading improvements".
--Thilo
Re: 2.2 release
Posted by Thilo Goetz <tw...@gmx.de>.
Marshall Schor wrote:
> Thilo Goetz wrote:
>> Hi all,
>>
>> how are we doing for our next release? I have a couple of minor
>> things I want to
>> commit, but nothing major. I'd like to propose the following schedule:
>>
>> 6/1: feature freeze, start testing, make sure documentation is up to date
>> 6/8: if no major bugs found, build release candidate and start vote
>>
>> We have a couple of major items in this release that we need to test
>> carefully:
>>
>> - the new Pear runtime
>> - the JCas class loading improvements and CAS reorg
>>
>> Anything else?
> Class loader switching :-) Shouldn't be too hard to do if I don't get
> swampped with other work next week.
> -Marshall
That's actually what I mean by "JCas class loading improvements".
--Thilo
Re: 2.2 release
Posted by Marshall Schor <ms...@schor.com>.
Thilo Goetz wrote:
> Hi all,
>
> how are we doing for our next release? I have a couple of minor
> things I want to
> commit, but nothing major. I'd like to propose the following schedule:
>
> 6/1: feature freeze, start testing, make sure documentation is up to date
> 6/8: if no major bugs found, build release candidate and start vote
>
> We have a couple of major items in this release that we need to test
> carefully:
>
> - the new Pear runtime
> - the JCas class loading improvements and CAS reorg
>
> Anything else?
Class loader switching :-) Shouldn't be too hard to do if I don't get
swampped with other work next week.
-Marshall