You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2007/10/19 17:02:47 UTC
next release, and CAS Impl refactoring
How about we target the next release freeze/start-of-test for Nov 5?
Between now and the next release, Thilo wants to do work on CAS
refactoring - to enable that, I suggest we agree to freeze **now** in
the trunk all feature enhancement/improvement changes, and only do bug
fixes (unless the changes are completely independent of Thilo's work -
such as for example adding some documentation to a non-CAS area). The
goal is to allow Thilo to "branch" the code base and do his work in
parallel, with minimal (we hope) impact on the future "merging".
We need a release manager for the next release. This involves reading
some web pages to see that we follow the right process, and then
reminding the others in the dev community to help out with testing,
etc. This work would start in November. For our first 2 releases,
Thilo has volunteered, (Thank You!), but I'm guessing he'd be happy for
someone else to take a turn. Any volunteers?
-Marshall
Re: next release, and CAS Impl refactoring
Posted by Eddie Epstein <ea...@gmail.com>.
Thanks Adam, will do in the next few days.
Eddie
On Nov 13, 2007 3:58 PM, Adam Lally <al...@alum.rpi.edu> wrote:
> On Nov 13, 2007 12:07 PM, Michael Baessler <mb...@michael-baessler.de>
> wrote:
> > I still see three unresolved issues for release 2.3 (2.2.1). If we want
> > to ship the release this year we should try to fix these issues soon.
> > The open issues are:
> > UIMA-598
> > UIMA-583
> > UIMA-529
> >
> > Volunteers?
> >
>
> I resolved UIMA-598 and assigned to Eddie to verify.
>
> -Adam
>
Re: next release, and CAS Impl refactoring
Posted by Michael Baessler <mb...@michael-baessler.de>.
Adam Lally wrote:
> On Nov 14, 2007 12:00 PM, Michael Baessler <mb...@michael-baessler.de> wrote:
>
>> OK the remaining open issues are:
>>
>> - UIMA-583 (https://issues.apache.org/jira/browse/UIMA-583)
>> I have already documented most of the issues mentioned in UIMA-583.
>> But I can't do all. Please look at the issue comment.
>>
>> - UIMA-529 (https://issues.apache.org/jira/browse/UIMA-529)
>> This issue is assigned to Marshall, since he is at ApacheCon, can
>> anybody else look at this issue?
>>
>>
>
> I added some javadocs for UIMA-583 and think we can be done with that
> now. I don't think I'm going to have time to look at UIMA-529. Does
> this need to be done for this release?
>
> -Adam
>
There are already changes committed for issue 529, so I think we should
finish this.
-- Michael
Re: next release, and CAS Impl refactoring
Posted by Adam Lally <al...@alum.rpi.edu>.
On Nov 14, 2007 12:00 PM, Michael Baessler <mb...@michael-baessler.de> wrote:
> OK the remaining open issues are:
>
> - UIMA-583 (https://issues.apache.org/jira/browse/UIMA-583)
> I have already documented most of the issues mentioned in UIMA-583.
> But I can't do all. Please look at the issue comment.
>
> - UIMA-529 (https://issues.apache.org/jira/browse/UIMA-529)
> This issue is assigned to Marshall, since he is at ApacheCon, can
> anybody else look at this issue?
>
I added some javadocs for UIMA-583 and think we can be done with that
now. I don't think I'm going to have time to look at UIMA-529. Does
this need to be done for this release?
-Adam
Re: next release, and CAS Impl refactoring
Posted by Michael Baessler <mb...@michael-baessler.de>.
Adam Lally wrote:
> On Nov 13, 2007 12:07 PM, Michael Baessler <mb...@michael-baessler.de> wrote:
>
>> I still see three unresolved issues for release 2.3 (2.2.1). If we want
>> to ship the release this year we should try to fix these issues soon.
>> The open issues are:
>> UIMA-598
>> UIMA-583
>> UIMA-529
>>
>> Volunteers?
>>
>>
>
> I resolved UIMA-598 and assigned to Eddie to verify.
>
> -Adam
>
OK the remaining open issues are:
- UIMA-583 (https://issues.apache.org/jira/browse/UIMA-583)
I have already documented most of the issues mentioned in UIMA-583.
But I can't do all. Please look at the issue comment.
- UIMA-529 (https://issues.apache.org/jira/browse/UIMA-529)
This issue is assigned to Marshall, since he is at ApacheCon, can
anybody else look at this issue?
-- Michael
Re: next release, and CAS Impl refactoring
Posted by Adam Lally <al...@alum.rpi.edu>.
On Nov 13, 2007 12:07 PM, Michael Baessler <mb...@michael-baessler.de> wrote:
> I still see three unresolved issues for release 2.3 (2.2.1). If we want
> to ship the release this year we should try to fix these issues soon.
> The open issues are:
> UIMA-598
> UIMA-583
> UIMA-529
>
> Volunteers?
>
I resolved UIMA-598 and assigned to Eddie to verify.
-Adam
Re: next release, and CAS Impl refactoring
Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler wrote:
> Adam Lally wrote:
>> On Nov 5, 2007 7:47 AM, Michael Baessler <mb...@michael-baessler.de>
>> wrote:
>>
>>> No replays for more than two weeks now... what does this mean?
>>> It is not necessary to do the release refresh, or we just found no
>>> volunteer?
>>> If we still think it is necessary to do the refresh I will do the
>>> release manager job this time.
>>>
>>>
>>
>> I still think we should do a release soon. However I think I was
>> supposed to look into UIMA-598 first and haven't found the time to do
>> it yet. The rest of this week isn't looking good either. :(
>>
> I changed the the fix version for this issue to 2.3 so that it appears
> in the list of issues that should be fixed for 2.3.
> Are there any others that have to be fixed for 2.3 and are currently
> not marked with fix version 2.3?
>
> -- Michael
I still see three unresolved issues for release 2.3 (2.2.1). If we want
to ship the release this year we should try to fix these issues soon.
The open issues are:
UIMA-598
UIMA-583
UIMA-529
Volunteers?
-- Michael
Re: next release, and CAS Impl refactoring
Posted by Michael Baessler <mb...@michael-baessler.de>.
Adam Lally wrote:
> On Nov 5, 2007 7:47 AM, Michael Baessler <mb...@michael-baessler.de> wrote:
>
>> No replays for more than two weeks now... what does this mean?
>> It is not necessary to do the release refresh, or we just found no
>> volunteer?
>> If we still think it is necessary to do the refresh I will do the
>> release manager job this time.
>>
>>
>
> I still think we should do a release soon. However I think I was
> supposed to look into UIMA-598 first and haven't found the time to do
> it yet. The rest of this week isn't looking good either. :(
>
I changed the the fix version for this issue to 2.3 so that it appears
in the list of issues that should be fixed for 2.3.
Are there any others that have to be fixed for 2.3 and are currently not
marked with fix version 2.3?
-- Michael
Re: next release, and CAS Impl refactoring
Posted by Adam Lally <al...@alum.rpi.edu>.
On Nov 5, 2007 7:47 AM, Michael Baessler <mb...@michael-baessler.de> wrote:
> No replays for more than two weeks now... what does this mean?
> It is not necessary to do the release refresh, or we just found no
> volunteer?
> If we still think it is necessary to do the refresh I will do the
> release manager job this time.
>
I still think we should do a release soon. However I think I was
supposed to look into UIMA-598 first and haven't found the time to do
it yet. The rest of this week isn't looking good either. :(
-Adam
Re: next release, and CAS Impl refactoring
Posted by Michael Baessler <mb...@michael-baessler.de>.
Thilo Goetz wrote:
> I'll help out with the next release of course. We should
> take the opportunity and add the delta between what's already
> documented and what's not to the documentation, so it's easy
> for any of us to be release manager for one or two releases.
>
> Relevant web pages include:
>
> http://incubator.apache.org/guides/releasemanagement.html
> http://incubator.apache.org/uima/distribution.html
> http://cwiki.apache.org/UIMA/release-plan.html
> and more info on our wiki.
>
> Let me know if you have any questions.
>
> --Thilo
>
> Marshall Schor wrote:
>
>> How about we target the next release freeze/start-of-test for Nov 5?
>>
>> Between now and the next release, Thilo wants to do work on CAS
>> refactoring - to enable that, I suggest we agree to freeze **now** in
>> the trunk all feature enhancement/improvement changes, and only do bug
>> fixes (unless the changes are completely independent of Thilo's work -
>> such as for example adding some documentation to a non-CAS area). The
>> goal is to allow Thilo to "branch" the code base and do his work in
>> parallel, with minimal (we hope) impact on the future "merging".
>>
>> We need a release manager for the next release. This involves reading
>> some web pages to see that we follow the right process, and then
>> reminding the others in the dev community to help out with testing,
>> etc. This work would start in November. For our first 2 releases,
>> Thilo has volunteered, (Thank You!), but I'm guessing he'd be happy for
>> someone else to take a turn. Any volunteers?
>>
>> -Marshall
>>
No replays for more than two weeks now... what does this mean?
It is not necessary to do the release refresh, or we just found no
volunteer?
If we still think it is necessary to do the refresh I will do the
release manager job this time.
-- Michael
Re: next release, and CAS Impl refactoring
Posted by Thilo Goetz <tw...@gmx.de>.
I'll help out with the next release of course. We should
take the opportunity and add the delta between what's already
documented and what's not to the documentation, so it's easy
for any of us to be release manager for one or two releases.
Relevant web pages include:
http://incubator.apache.org/guides/releasemanagement.html
http://incubator.apache.org/uima/distribution.html
http://cwiki.apache.org/UIMA/release-plan.html
and more info on our wiki.
Let me know if you have any questions.
--Thilo
Marshall Schor wrote:
> How about we target the next release freeze/start-of-test for Nov 5?
>
> Between now and the next release, Thilo wants to do work on CAS
> refactoring - to enable that, I suggest we agree to freeze **now** in
> the trunk all feature enhancement/improvement changes, and only do bug
> fixes (unless the changes are completely independent of Thilo's work -
> such as for example adding some documentation to a non-CAS area). The
> goal is to allow Thilo to "branch" the code base and do his work in
> parallel, with minimal (we hope) impact on the future "merging".
>
> We need a release manager for the next release. This involves reading
> some web pages to see that we follow the right process, and then
> reminding the others in the dev community to help out with testing,
> etc. This work would start in November. For our first 2 releases,
> Thilo has volunteered, (Thank You!), but I'm guessing he'd be happy for
> someone else to take a turn. Any volunteers?
>
> -Marshall