You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Martin Toepfer <ma...@uni-wuerzburg.de> on 2014/02/13 19:28:01 UTC
[VOTE] Release Apache UIMA Ruta 2.2.0 RC2
Hi,
the second release candidate of Apache UIMA Ruta v2.2.0 is ready for voting.
Changes in RC2 since RC1:
- added NOTICE entries from dependencies in ruta-ep-engine
- fixed LICENSE file of ruta-ep-ide
- fixed problem with missing descriptor in TextRuler
- fixed problem with MARKONCE action in workbench
- fixed warnings of maven build of ruta-ep-engine
- fixed antlr warning in ruta-ep-ide
- added exclusions for stringtemplate library
- removed redundant exclusions
Staging repository:
https://repository.apache.org/content/repositories/orgapacheuima-1008/
SVN tag:
https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.2.0-rc2
Update site:
http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/eclipse-update-site/ruta
Archive with all sources:
http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/ruta-2.2.0-source-release.zip
Overall 54 issues have been fixed for this release.
They can be found in the RELEASE_NOTES.html and here:
https://issues.apache.org/jira/browse/UIMA-3609?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.2.0ruta%22%20AND%20component%20%3D%20ruta%20AND%20status%20in%20%28Resolved%2C%20Closed%29
Major Changes in this Release
UIMA Ruta Language and Analysis Engine:
- Major performance improvements
- Improved import type functionality and handling of ambiguous short names
- Options to determine where the next match should start
- Requires at least Java 6
- Many bug fixes
UIMA Ruta Workbench:
- Smaller improvements in many views
- Many bug fixes
ONLY FOR REVIEWING:
Documentation (pdf file):
http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/tools.ruta.book.pdf
Please vote on release:
[ ] +1 OK to release
[ ] 0 Don't care
[ ] -1 Not OK to release, because ...
Thanks.
Martin
Re: [VOTE][CANCEL] Release Apache UIMA Ruta 2.2.0 RC2
Posted by Martin Toepfer <ma...@uni-wuerzburg.de>.
I agree. The vote for RC2 is canceled; Peter is going to address the
problems. We plan to provide RC3 as soon as possible. I guess this will
be within one or two weeks.
Martin
Am 18.02.2014 13:58, schrieb Peter Klügl:
> I know I voted +1, but I wonder if it is reasonable to create a new RC,
> which includes:
> UIMA-3628 Loading scripts/descriptors in Ruta with incorrect paths
> UIMA-3627 Replace old screenshot in Ruta documentation
> UIMA-3569 Allow extensions for complete block constructs in Ruta
> UIMA-3622 Formatter in Ruta editor duplicates declare keywords
> UIMA-3621 Improve license/notice files in Ruta
>
> It's probably better to release something that is cleaner and more stable...
>
> Best,
>
> Peter
>
>
>
> Am 17.02.2014 10:33, schrieb Peter Klügl:
>> Hi,
>>
>> Am 15.02.2014 22:51, schrieb Marshall Schor:
>>> Verified signatures
>>> verify signatures / md5 / sha1 in repository - ruta core -OK. (Got Martin's key
>>> from mit pgp server)
>>> verify signatures for source-release
>>>
>>> The verification says Martin's key is not part of a trust ring - I would
>>> recommend cross-signing your key by those physically near you :-)
>> Yes, we already talked about that :-)
>>
>>> Checked issues fixed - looks ok
>>>
>>> Did a build from sources - OK
>>>
>>> compared sources / svn tag - OK
>>>
>>> I installed the ruta plugins into a fresh 4.3.1 Eclipse - OK. I did this
>>> trick: I first "added" the main UIMA eclipse update site
>>> (http://www.apache.org/dist/uima/eclipse-update-site), but I didn't install
>>> anything. Then I put in the RUTA site, and left the box checked to have install
>>> contact all the sites when looking for other artifacts; the install process then
>>> contacted the main UIMA site for the plugins it needed - worked like a charm :-)
>>>
>>> I noticed that some but not all of the internal projects within the examples
>>> folder (example-project, extensions-project, TextRulerExample) have their own
>>> license/notice - which can be a maintenance issue - for example, these have a 2013
>>> end date in the Notice part. Normally, the License/Notice files are put at the
>>> top level of a distribution; I'm not sure why they're here.
>> I will create an issue for the notice/license problems you found.
>>
>> The projects are Ruta projects and are not built with maven. They can be
>> checked out from the scm, and if build, there will be no notice/license
>> file otherwise.
>>
>>
>>> The NOTICE file in many places has duplicate info for creative commons that's
>>> also part of license file. Normally any information that's already in the
>>> License file should not be also duplicated in the Notices file. The Notices
>>> file is for things which are not part of the license terms, but need to be
>>> present (such as copyrights). See
>>>
>>> https://www.apache.org/dev/licensing-howto.html#simple
>>>
>>> where it says, in part:
>>> However, elements such as the copyright notifications embedded within BSD
>>> and MIT licenses need not be duplicated in NOTICE -- it suffices to leave those
>>> notices in their original locations.
>> Is it possible that the best practice has changed somehow? I am quite
>> sure that I had to add the notice because of the license.
>>
>> Peter
>>
Re: [VOTE] Release Apache UIMA Ruta 2.2.0 RC2
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
I know I voted +1, but I wonder if it is reasonable to create a new RC,
which includes:
UIMA-3628 Loading scripts/descriptors in Ruta with incorrect paths
UIMA-3627 Replace old screenshot in Ruta documentation
UIMA-3569 Allow extensions for complete block constructs in Ruta
UIMA-3622 Formatter in Ruta editor duplicates declare keywords
UIMA-3621 Improve license/notice files in Ruta
It's probably better to release something that is cleaner and more stable...
Best,
Peter
Am 17.02.2014 10:33, schrieb Peter Klügl:
> Hi,
>
> Am 15.02.2014 22:51, schrieb Marshall Schor:
>> Verified signatures
>> verify signatures / md5 / sha1 in repository - ruta core -OK. (Got Martin's key
>> from mit pgp server)
>> verify signatures for source-release
>>
>> The verification says Martin's key is not part of a trust ring - I would
>> recommend cross-signing your key by those physically near you :-)
> Yes, we already talked about that :-)
>
>> Checked issues fixed - looks ok
>>
>> Did a build from sources - OK
>>
>> compared sources / svn tag - OK
>>
>> I installed the ruta plugins into a fresh 4.3.1 Eclipse - OK. I did this
>> trick: I first "added" the main UIMA eclipse update site
>> (http://www.apache.org/dist/uima/eclipse-update-site), but I didn't install
>> anything. Then I put in the RUTA site, and left the box checked to have install
>> contact all the sites when looking for other artifacts; the install process then
>> contacted the main UIMA site for the plugins it needed - worked like a charm :-)
>>
>> I noticed that some but not all of the internal projects within the examples
>> folder (example-project, extensions-project, TextRulerExample) have their own
>> license/notice - which can be a maintenance issue - for example, these have a 2013
>> end date in the Notice part. Normally, the License/Notice files are put at the
>> top level of a distribution; I'm not sure why they're here.
> I will create an issue for the notice/license problems you found.
>
> The projects are Ruta projects and are not built with maven. They can be
> checked out from the scm, and if build, there will be no notice/license
> file otherwise.
>
>
>> The NOTICE file in many places has duplicate info for creative commons that's
>> also part of license file. Normally any information that's already in the
>> License file should not be also duplicated in the Notices file. The Notices
>> file is for things which are not part of the license terms, but need to be
>> present (such as copyrights). See
>>
>> https://www.apache.org/dev/licensing-howto.html#simple
>>
>> where it says, in part:
>> However, elements such as the copyright notifications embedded within BSD
>> and MIT licenses need not be duplicated in NOTICE -- it suffices to leave those
>> notices in their original locations.
> Is it possible that the best practice has changed somehow? I am quite
> sure that I had to add the notice because of the license.
>
> Peter
>
Re: [VOTE] Release Apache UIMA Ruta 2.2.0 RC2
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
Hi,
Am 15.02.2014 22:51, schrieb Marshall Schor:
> Verified signatures
> verify signatures / md5 / sha1 in repository - ruta core -OK. (Got Martin's key
> from mit pgp server)
> verify signatures for source-release
>
> The verification says Martin's key is not part of a trust ring - I would
> recommend cross-signing your key by those physically near you :-)
Yes, we already talked about that :-)
> Checked issues fixed - looks ok
>
> Did a build from sources - OK
>
> compared sources / svn tag - OK
>
> I installed the ruta plugins into a fresh 4.3.1 Eclipse - OK. I did this
> trick: I first "added" the main UIMA eclipse update site
> (http://www.apache.org/dist/uima/eclipse-update-site), but I didn't install
> anything. Then I put in the RUTA site, and left the box checked to have install
> contact all the sites when looking for other artifacts; the install process then
> contacted the main UIMA site for the plugins it needed - worked like a charm :-)
>
> I noticed that some but not all of the internal projects within the examples
> folder (example-project, extensions-project, TextRulerExample) have their own
> license/notice - which can be a maintenance issue - for example, these have a 2013
> end date in the Notice part. Normally, the License/Notice files are put at the
> top level of a distribution; I'm not sure why they're here.
I will create an issue for the notice/license problems you found.
The projects are Ruta projects and are not built with maven. They can be
checked out from the scm, and if build, there will be no notice/license
file otherwise.
> The NOTICE file in many places has duplicate info for creative commons that's
> also part of license file. Normally any information that's already in the
> License file should not be also duplicated in the Notices file. The Notices
> file is for things which are not part of the license terms, but need to be
> present (such as copyrights). See
>
> https://www.apache.org/dev/licensing-howto.html#simple
>
> where it says, in part:
> However, elements such as the copyright notifications embedded within BSD
> and MIT licenses need not be duplicated in NOTICE -- it suffices to leave those
> notices in their original locations.
Is it possible that the best practice has changed somehow? I am quite
sure that I had to add the notice because of the license.
Peter
Re: [VOTE] Release Apache UIMA Ruta 2.2.0 RC2
Posted by Marshall Schor <ms...@schor.com>.
Verified signatures
verify signatures / md5 / sha1 in repository - ruta core -OK. (Got Martin's key
from mit pgp server)
verify signatures for source-release
The verification says Martin's key is not part of a trust ring - I would
recommend cross-signing your key by those physically near you :-)
Checked issues fixed - looks ok
Did a build from sources - OK
compared sources / svn tag - OK
I installed the ruta plugins into a fresh 4.3.1 Eclipse - OK. I did this
trick: I first "added" the main UIMA eclipse update site
(http://www.apache.org/dist/uima/eclipse-update-site), but I didn't install
anything. Then I put in the RUTA site, and left the box checked to have install
contact all the sites when looking for other artifacts; the install process then
contacted the main UIMA site for the plugins it needed - worked like a charm :-)
I noticed that some but not all of the internal projects within the examples
folder (example-project, extensions-project, TextRulerExample) have their own
license/notice - which can be a maintenance issue - for example, these have a 2013
end date in the Notice part. Normally, the License/Notice files are put at the
top level of a distribution; I'm not sure why they're here.
The NOTICE file in many places has duplicate info for creative commons that's
also part of license file. Normally any information that's already in the
License file should not be also duplicated in the Notices file. The Notices
file is for things which are not part of the license terms, but need to be
present (such as copyrights). See
https://www.apache.org/dev/licensing-howto.html#simple
where it says, in part:
However, elements such as the copyright notifications embedded within BSD
and MIT licenses need not be duplicated in NOTICE -- it suffices to leave those
notices in their original locations.
Looks like the build process for the individual project Javadoc jars is
including the license /notice files appropriate for jars containing Icons from
Mark James, but those Jars don't have those icons.
Also the Mark James attribution in both notice and license has an extra "the" in
front of Mark James:
This product contains icons developed by the Mark James --- should read:
This product contains icons developed by Mark James
These NOTICE issues are minor, and not release blockers, I think.
[x] +1 OK to release
-Marshall
Re: [VOTE] Release Apache UIMA Ruta 2.2.0 RC2
Posted by Peter Klügl <pk...@uni-wuerzburg.de>.
compared svn-tag with source-release - OK
mvn clean install svn-tag - OK
mvn clean install source-release - OK
checked license/notice of ruta-ep-ide(-sources) - OK
checked license/notice of ruta-ep-engine(-sources) - OK
the notice file of ruta-ep-engine-sources contains a notice of the
university of würzburg, but I don't think that's a blocker
installed workbench in kepler sr1 with uima features present - OK
created project and tested a simple script - OK
import ExampleProject of source-release and applied tests - OK
import TextRulerExample of source release and induced some rules - OK
warnings for javadoc: will hopefully be fixed in the next release.
problems verifying md5/sha1 (cannot find file due to line break)
[X] +1 OK to release
Peter
Am 13.02.2014 19:28, schrieb Martin Toepfer:
> Hi,
>
> the second release candidate of Apache UIMA Ruta v2.2.0 is ready for
> voting.
>
> Changes in RC2 since RC1:
> - added NOTICE entries from dependencies in ruta-ep-engine
> - fixed LICENSE file of ruta-ep-ide
> - fixed problem with missing descriptor in TextRuler
> - fixed problem with MARKONCE action in workbench
> - fixed warnings of maven build of ruta-ep-engine
> - fixed antlr warning in ruta-ep-ide
> - added exclusions for stringtemplate library
> - removed redundant exclusions
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapacheuima-1008/
>
> SVN tag:
> https://svn.apache.org/repos/asf/uima/ruta/tags/ruta-2.2.0-rc2
>
> Update site:
> http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/eclipse-update-site/ruta
>
>
> Archive with all sources:
> http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/ruta-2.2.0-source-release.zip
>
>
> Overall 54 issues have been fixed for this release.
> They can be found in the RELEASE_NOTES.html and here:
> https://issues.apache.org/jira/browse/UIMA-3609?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.2.0ruta%22%20AND%20component%20%3D%20ruta%20AND%20status%20in%20%28Resolved%2C%20Closed%29
>
>
> Major Changes in this Release
>
> UIMA Ruta Language and Analysis Engine:
> - Major performance improvements
> - Improved import type functionality and handling of ambiguous short
> names
> - Options to determine where the next match should start
> - Requires at least Java 6
> - Many bug fixes
>
> UIMA Ruta Workbench:
> - Smaller improvements in many views
> - Many bug fixes
>
>
> ONLY FOR REVIEWING:
>
> Documentation (pdf file):
> http://people.apache.org/~mtoepfer/uima-releases/ruta-2.2.0-rc2/tools.ruta.book.pdf
>
>
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> Martin
>