You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Peter Klügl <pe...@averbis.com> on 2017/02/24 14:08:43 UTC
UIMA Ruta 2.5.1 vs 2.6.0
Simply put, fixing UIMA-5316 was some sort of refactoring where two
classes have been removed.
A third class was a bit extended to support the use cases of the prior
two classes. As a consequence, complete new functionality was
introduced: matching on feature values as annotation expression. And
there is only a small step toward using conditions at annotation
expressions. This is actually a functionality a user asked for in
2008/2009 or something, and there was no way at all to implement it.
Well, now after all the refactorings (especially introducing annotation
expressions), both new features are implemented almost by accident :-)
Here are two examples of what I am talking about:
Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
(looks trivial, but has far reaching consequences for rule engineering)
I think both features could be really useful for many users, and
therefore I will include them right now. I am also thinking about
implementing a prototype of optimization of the internal indexing based
on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
feedback, or if I have enough time to evaluate it, there is also the
memory optimization of RutaBasic.
Even with only one of these features, the next release is not a
maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
and the next RC will be 2.6.0 RC1.
Any questions/objections/opinions?
Best,
Peter
Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>
>
> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>> Hi,
>>
>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>
>> Major changes in this release:
>>
>> UIMA Ruta Language and Analysis Engine:
>> - Typesystem descriptors with JCasGen classes are located in separate
>> artefact
>> - Minimal support of feature structures in feature match expressions
>> - Many bug fixes and improvements, especially for label expressions
>>
>> UIMA Ruta Workbench:
>> - Direct debugging of launched scripts in Java is supported
>> - Improved error messages in launcher
>> - Removed restriction of classpath size causing problems in launcher
>> - Deactivated noVM preference
>> - Launcher uses project encoding
>> - Bug fixes
>>
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>
>> SVN tag:
>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>
>> Update site:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>
>> Archive with all sources:
>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>
>> Overall 32 issues have been fixed for this release
>> (1 duplicates, 1 not a problem).
>> They can be found in the RELEASE_NOTES.html.
>>
>> ... and here:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>> Please vote on release:
>>
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [ ] -1 Not OK to release, because ...
>>
>> Thanks.
>>
>> Peter
>>
>>
Re: UIMA Ruta 2.5.1 vs 2.6.0
Posted by Peter Klügl <pe...@averbis.com>.
Good point. I have planned to switch too but forgot about it.
Peter
Am 24.02.2017 um 17:54 schrieb Marshall Schor:
> I recently switched the uimaj-core / parent poms to use a new approach for
> managing API changes; this approach produces a report "api-chage-report.html"
> which I now include in the assemblies, like the issues-fixed report.
>
> This report is much clearer about what gets changed, allows detailed control to
> avoid "noise" messages, and is useful for end users too, to see what got changed.
>
> -Marshall
>
>
> On 2/24/2017 9:08 AM, Peter Kl�gl wrote:
>> Simply put, fixing UIMA-5316 was some sort of refactoring where two
>> classes have been removed.
>>
>> A third class was a bit extended to support the use cases of the prior
>> two classes. As a consequence, complete new functionality was
>> introduced: matching on feature values as annotation expression. And
>> there is only a small step toward using conditions at annotation
>> expressions. This is actually a functionality a user asked for in
>> 2008/2009 or something, and there was no way at all to implement it.
>> Well, now after all the refactorings (especially introducing annotation
>> expressions), both new features are implemented almost by accident :-)
>>
>> Here are two examples of what I am talking about:
>>
>> Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
>>
>> Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
>>
>> (looks trivial, but has far reaching consequences for rule engineering)
>>
>> I think both features could be really useful for many users, and
>> therefore I will include them right now. I am also thinking about
>> implementing a prototype of optimization of the internal indexing based
>> on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
>> feedback, or if I have enough time to evaluate it, there is also the
>> memory optimization of RutaBasic.
>>
>>
>> Even with only one of these features, the next release is not a
>> maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
>> and the next RC will be 2.6.0 RC1.
>>
>>
>> Any questions/objections/opinions?
>>
>>
>> Best,
>>
>>
>> Peter
>>
>>
>>
>>
>> Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
>>> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>>>
>>>
>>> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>>>> Hi,
>>>>
>>>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>>>
>>>> Major changes in this release:
>>>>
>>>> UIMA Ruta Language and Analysis Engine:
>>>> - Typesystem descriptors with JCasGen classes are located in separate
>>>> artefact
>>>> - Minimal support of feature structures in feature match expressions
>>>> - Many bug fixes and improvements, especially for label expressions
>>>>
>>>> UIMA Ruta Workbench:
>>>> - Direct debugging of launched scripts in Java is supported
>>>> - Improved error messages in launcher
>>>> - Removed restriction of classpath size causing problems in launcher
>>>> - Deactivated noVM preference
>>>> - Launcher uses project encoding
>>>> - Bug fixes
>>>>
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>>>
>>>> SVN tag:
>>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>>>
>>>> Update site:
>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>>>
>>>> Archive with all sources:
>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>>>
>>>> Overall 32 issues have been fixed for this release
>>>> (1 duplicates, 1 not a problem).
>>>> They can be found in the RELEASE_NOTES.html.
>>>>
>>>> ... and here:
>>>>
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>>> Please vote on release:
>>>>
>>>> [ ] +1 OK to release
>>>> [ ] 0 Don't care
>>>> [ ] -1 Not OK to release, because ...
>>>>
>>>> Thanks.
>>>>
>>>> Peter
>>>>
>>>>
Re: UIMA Ruta 2.5.1 vs 2.6.0
Posted by Peter Klügl <pe...@averbis.com>.
There is obviously a problem with my svn client. It did not add the file
but shows no diff.
I found it in the repo. Thanks Marshall.
Peter
Am 27.02.2017 um 20:42 schrieb Marshall Schor:
> yes, I have added groovy post-processing - it drops .impl., .internal. etc.
>
> You can find it in the uimaj-parent project, under src/main/groovy/api-report.groovy
>
> Cheers. -Marshall
>
>
> On 2/27/2017 9:10 AM, Peter Kl�gl wrote:
>> I wonder if you have added some postprocessing with api-report.groovy. I
>> cannot find it.
>>
>>
>> Best,
>>
>>
>> Peter
>>
>>
>> Am 24.02.2017 um 17:54 schrieb Marshall Schor:
>>> I recently switched the uimaj-core / parent poms to use a new approach for
>>> managing API changes; this approach produces a report "api-chage-report.html"
>>> which I now include in the assemblies, like the issues-fixed report.
>>>
>>> This report is much clearer about what gets changed, allows detailed control to
>>> avoid "noise" messages, and is useful for end users too, to see what got changed.
>>>
>>> -Marshall
>>>
>>>
>>> On 2/24/2017 9:08 AM, Peter Kl�gl wrote:
>>>> Simply put, fixing UIMA-5316 was some sort of refactoring where two
>>>> classes have been removed.
>>>>
>>>> A third class was a bit extended to support the use cases of the prior
>>>> two classes. As a consequence, complete new functionality was
>>>> introduced: matching on feature values as annotation expression. And
>>>> there is only a small step toward using conditions at annotation
>>>> expressions. This is actually a functionality a user asked for in
>>>> 2008/2009 or something, and there was no way at all to implement it.
>>>> Well, now after all the refactorings (especially introducing annotation
>>>> expressions), both new features are implemented almost by accident :-)
>>>>
>>>> Here are two examples of what I am talking about:
>>>>
>>>> Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
>>>>
>>>> Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
>>>>
>>>> (looks trivial, but has far reaching consequences for rule engineering)
>>>>
>>>> I think both features could be really useful for many users, and
>>>> therefore I will include them right now. I am also thinking about
>>>> implementing a prototype of optimization of the internal indexing based
>>>> on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
>>>> feedback, or if I have enough time to evaluate it, there is also the
>>>> memory optimization of RutaBasic.
>>>>
>>>>
>>>> Even with only one of these features, the next release is not a
>>>> maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
>>>> and the next RC will be 2.6.0 RC1.
>>>>
>>>>
>>>> Any questions/objections/opinions?
>>>>
>>>>
>>>> Best,
>>>>
>>>>
>>>> Peter
>>>>
>>>>
>>>>
>>>>
>>>> Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
>>>>> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>>>>>
>>>>>
>>>>> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>>>>>> Hi,
>>>>>>
>>>>>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>>>>>
>>>>>> Major changes in this release:
>>>>>>
>>>>>> UIMA Ruta Language and Analysis Engine:
>>>>>> - Typesystem descriptors with JCasGen classes are located in separate
>>>>>> artefact
>>>>>> - Minimal support of feature structures in feature match expressions
>>>>>> - Many bug fixes and improvements, especially for label expressions
>>>>>>
>>>>>> UIMA Ruta Workbench:
>>>>>> - Direct debugging of launched scripts in Java is supported
>>>>>> - Improved error messages in launcher
>>>>>> - Removed restriction of classpath size causing problems in launcher
>>>>>> - Deactivated noVM preference
>>>>>> - Launcher uses project encoding
>>>>>> - Bug fixes
>>>>>>
>>>>>>
>>>>>> Staging repository:
>>>>>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>>>>>
>>>>>> SVN tag:
>>>>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>>>>>
>>>>>> Update site:
>>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>>>>>
>>>>>> Archive with all sources:
>>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>>>>>
>>>>>> Overall 32 issues have been fixed for this release
>>>>>> (1 duplicates, 1 not a problem).
>>>>>> They can be found in the RELEASE_NOTES.html.
>>>>>>
>>>>>> ... and here:
>>>>>>
>>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>>>>> Please vote on release:
>>>>>>
>>>>>> [ ] +1 OK to release
>>>>>> [ ] 0 Don't care
>>>>>> [ ] -1 Not OK to release, because ...
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> Peter
>>>>>>
>>>>>>
Re: UIMA Ruta 2.5.1 vs 2.6.0
Posted by Marshall Schor <ms...@schor.com>.
yes, I have added groovy post-processing - it drops .impl., .internal. etc.
You can find it in the uimaj-parent project, under src/main/groovy/api-report.groovy
Cheers. -Marshall
On 2/27/2017 9:10 AM, Peter Kl�gl wrote:
> I wonder if you have added some postprocessing with api-report.groovy. I
> cannot find it.
>
>
> Best,
>
>
> Peter
>
>
> Am 24.02.2017 um 17:54 schrieb Marshall Schor:
>> I recently switched the uimaj-core / parent poms to use a new approach for
>> managing API changes; this approach produces a report "api-chage-report.html"
>> which I now include in the assemblies, like the issues-fixed report.
>>
>> This report is much clearer about what gets changed, allows detailed control to
>> avoid "noise" messages, and is useful for end users too, to see what got changed.
>>
>> -Marshall
>>
>>
>> On 2/24/2017 9:08 AM, Peter Kl�gl wrote:
>>> Simply put, fixing UIMA-5316 was some sort of refactoring where two
>>> classes have been removed.
>>>
>>> A third class was a bit extended to support the use cases of the prior
>>> two classes. As a consequence, complete new functionality was
>>> introduced: matching on feature values as annotation expression. And
>>> there is only a small step toward using conditions at annotation
>>> expressions. This is actually a functionality a user asked for in
>>> 2008/2009 or something, and there was no way at all to implement it.
>>> Well, now after all the refactorings (especially introducing annotation
>>> expressions), both new features are implemented almost by accident :-)
>>>
>>> Here are two examples of what I am talking about:
>>>
>>> Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
>>>
>>> Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
>>>
>>> (looks trivial, but has far reaching consequences for rule engineering)
>>>
>>> I think both features could be really useful for many users, and
>>> therefore I will include them right now. I am also thinking about
>>> implementing a prototype of optimization of the internal indexing based
>>> on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
>>> feedback, or if I have enough time to evaluate it, there is also the
>>> memory optimization of RutaBasic.
>>>
>>>
>>> Even with only one of these features, the next release is not a
>>> maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
>>> and the next RC will be 2.6.0 RC1.
>>>
>>>
>>> Any questions/objections/opinions?
>>>
>>>
>>> Best,
>>>
>>>
>>> Peter
>>>
>>>
>>>
>>>
>>> Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
>>>> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>>>>
>>>>
>>>> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>>>>> Hi,
>>>>>
>>>>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>>>>
>>>>> Major changes in this release:
>>>>>
>>>>> UIMA Ruta Language and Analysis Engine:
>>>>> - Typesystem descriptors with JCasGen classes are located in separate
>>>>> artefact
>>>>> - Minimal support of feature structures in feature match expressions
>>>>> - Many bug fixes and improvements, especially for label expressions
>>>>>
>>>>> UIMA Ruta Workbench:
>>>>> - Direct debugging of launched scripts in Java is supported
>>>>> - Improved error messages in launcher
>>>>> - Removed restriction of classpath size causing problems in launcher
>>>>> - Deactivated noVM preference
>>>>> - Launcher uses project encoding
>>>>> - Bug fixes
>>>>>
>>>>>
>>>>> Staging repository:
>>>>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>>>>
>>>>> SVN tag:
>>>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>>>>
>>>>> Update site:
>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>>>>
>>>>> Archive with all sources:
>>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>>>>
>>>>> Overall 32 issues have been fixed for this release
>>>>> (1 duplicates, 1 not a problem).
>>>>> They can be found in the RELEASE_NOTES.html.
>>>>>
>>>>> ... and here:
>>>>>
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>>>> Please vote on release:
>>>>>
>>>>> [ ] +1 OK to release
>>>>> [ ] 0 Don't care
>>>>> [ ] -1 Not OK to release, because ...
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Peter
>>>>>
>>>>>
>
Re: UIMA Ruta 2.5.1 vs 2.6.0
Posted by Peter Klügl <pe...@averbis.com>.
I wonder if you have added some postprocessing with api-report.groovy. I
cannot find it.
Best,
Peter
Am 24.02.2017 um 17:54 schrieb Marshall Schor:
> I recently switched the uimaj-core / parent poms to use a new approach for
> managing API changes; this approach produces a report "api-chage-report.html"
> which I now include in the assemblies, like the issues-fixed report.
>
> This report is much clearer about what gets changed, allows detailed control to
> avoid "noise" messages, and is useful for end users too, to see what got changed.
>
> -Marshall
>
>
> On 2/24/2017 9:08 AM, Peter Kl�gl wrote:
>> Simply put, fixing UIMA-5316 was some sort of refactoring where two
>> classes have been removed.
>>
>> A third class was a bit extended to support the use cases of the prior
>> two classes. As a consequence, complete new functionality was
>> introduced: matching on feature values as annotation expression. And
>> there is only a small step toward using conditions at annotation
>> expressions. This is actually a functionality a user asked for in
>> 2008/2009 or something, and there was no way at all to implement it.
>> Well, now after all the refactorings (especially introducing annotation
>> expressions), both new features are implemented almost by accident :-)
>>
>> Here are two examples of what I am talking about:
>>
>> Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
>>
>> Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
>>
>> (looks trivial, but has far reaching consequences for rule engineering)
>>
>> I think both features could be really useful for many users, and
>> therefore I will include them right now. I am also thinking about
>> implementing a prototype of optimization of the internal indexing based
>> on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
>> feedback, or if I have enough time to evaluate it, there is also the
>> memory optimization of RutaBasic.
>>
>>
>> Even with only one of these features, the next release is not a
>> maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
>> and the next RC will be 2.6.0 RC1.
>>
>>
>> Any questions/objections/opinions?
>>
>>
>> Best,
>>
>>
>> Peter
>>
>>
>>
>>
>> Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
>>> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>>>
>>>
>>> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>>>> Hi,
>>>>
>>>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>>>
>>>> Major changes in this release:
>>>>
>>>> UIMA Ruta Language and Analysis Engine:
>>>> - Typesystem descriptors with JCasGen classes are located in separate
>>>> artefact
>>>> - Minimal support of feature structures in feature match expressions
>>>> - Many bug fixes and improvements, especially for label expressions
>>>>
>>>> UIMA Ruta Workbench:
>>>> - Direct debugging of launched scripts in Java is supported
>>>> - Improved error messages in launcher
>>>> - Removed restriction of classpath size causing problems in launcher
>>>> - Deactivated noVM preference
>>>> - Launcher uses project encoding
>>>> - Bug fixes
>>>>
>>>>
>>>> Staging repository:
>>>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>>>
>>>> SVN tag:
>>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>>>
>>>> Update site:
>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>>>
>>>> Archive with all sources:
>>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>>>
>>>> Overall 32 issues have been fixed for this release
>>>> (1 duplicates, 1 not a problem).
>>>> They can be found in the RELEASE_NOTES.html.
>>>>
>>>> ... and here:
>>>>
>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>>> Please vote on release:
>>>>
>>>> [ ] +1 OK to release
>>>> [ ] 0 Don't care
>>>> [ ] -1 Not OK to release, because ...
>>>>
>>>> Thanks.
>>>>
>>>> Peter
>>>>
>>>>
Re: UIMA Ruta 2.5.1 vs 2.6.0
Posted by Marshall Schor <ms...@schor.com>.
I recently switched the uimaj-core / parent poms to use a new approach for
managing API changes; this approach produces a report "api-chage-report.html"
which I now include in the assemblies, like the issues-fixed report.
This report is much clearer about what gets changed, allows detailed control to
avoid "noise" messages, and is useful for end users too, to see what got changed.
-Marshall
On 2/24/2017 9:08 AM, Peter Kl�gl wrote:
> Simply put, fixing UIMA-5316 was some sort of refactoring where two
> classes have been removed.
>
> A third class was a bit extended to support the use cases of the prior
> two classes. As a consequence, complete new functionality was
> introduced: matching on feature values as annotation expression. And
> there is only a small step toward using conditions at annotation
> expressions. This is actually a functionality a user asked for in
> 2008/2009 or something, and there was no way at all to implement it.
> Well, now after all the refactorings (especially introducing annotation
> expressions), both new features are implemented almost by accident :-)
>
> Here are two examples of what I am talking about:
>
> Document{-> CREATE(Struct1, "a" = SW.begin == 8)};
>
> Document{-> CREATE(Struct1, "a" = SW{REGEXP("a.*")})};
>
> (looks trivial, but has far reaching consequences for rule engineering)
>
> I think both features could be really useful for many users, and
> therefore I will include them right now. I am also thinking about
> implementing a prototype of optimization of the internal indexing based
> on the type usage in the script (UIMA-5219 + UIMA-5220). And if there is
> feedback, or if I have enough time to evaluate it, there is also the
> memory optimization of RutaBasic.
>
>
> Even with only one of these features, the next release is not a
> maintenance release anymore, but a minor release. Thus, I'll skip 2.5.1
> and the next RC will be 2.6.0 RC1.
>
>
> Any questions/objections/opinions?
>
>
> Best,
>
>
> Peter
>
>
>
>
> Am 14.02.2017 um 13:59 schrieb Peter Kl�gl:
>> UIMA-5316 is serious enough to cancel the vote and create a new RC :-(
>>
>>
>> Am 03.02.2017 um 12:14 schrieb Peter Kl�gl:
>>> Hi,
>>>
>>> the first release candidate of Apache UIMA Ruta v2.5.1 is ready for voting.
>>>
>>> Major changes in this release:
>>>
>>> UIMA Ruta Language and Analysis Engine:
>>> - Typesystem descriptors with JCasGen classes are located in separate
>>> artefact
>>> - Minimal support of feature structures in feature match expressions
>>> - Many bug fixes and improvements, especially for label expressions
>>>
>>> UIMA Ruta Workbench:
>>> - Direct debugging of launched scripts in Java is supported
>>> - Improved error messages in launcher
>>> - Removed restriction of classpath size causing problems in launcher
>>> - Deactivated noVM preference
>>> - Launcher uses project encoding
>>> - Bug fixes
>>>
>>>
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/orgapacheuima-1121/
>>>
>>> SVN tag:
>>> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.5.1
>>>
>>> Update site:
>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/eclipse-update-site/ruta/
>>>
>>> Archive with all sources:
>>> https://dist.apache.org/repos/dist/dev/uima/ruta-2.5.1-rc1/ruta-2.5.1-source-release.zip
>>>
>>> Overall 32 issues have been fixed for this release
>>> (1 duplicates, 1 not a problem).
>>> They can be found in the RELEASE_NOTES.html.
>>>
>>> ... and here:
>>>
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.5.1ruta%20AND%20component%20%3D%20ruta%20ORDER%20BY%20created%20DESC
>>> Please vote on release:
>>>
>>> [ ] +1 OK to release
>>> [ ] 0 Don't care
>>> [ ] -1 Not OK to release, because ...
>>>
>>> Thanks.
>>>
>>> Peter
>>>
>>>
>