Thanks Peter!

The NOTICE file of the binary release needs to be fixed indeed. I wonder why we 
missed that in the release of uimaFIT 2.0.0.

Will do another RC and also fix the other two issues.

Cheers,

-- Richard

On 04.06.2014, at 10:06, Peter Klügl <[email protected]> wrote:

> compared svn-tag to source release
> - eclipse "compare with" "each other" reports many differences, but I
> found no critical ones
> 
> mvn install svn-tag - OK
> mvn install source-release - OK
> (Windows, Java 1.6)
> 
> checked license/notice in binary-release - maybe OK
> (I am still not really sure about the requirements)
> The notice file in commons-logging-1.1.1 mentions something, but it is
> not reproduced in the notice file of the release.
> The notice about IBM and UIMA is not mentioned in the notice file, but
> UIMA artifacts are included.
> (if there is a new rc...)
> 
> mvn install ruta using staged artifacts - OK
> 
> [X] +1 OK to release
> 
> Peter
> 
> Am 03.06.2014 16:27, schrieb Richard Eckart de Castilho:
>> Hi,
>> 
>> I've posted the uimaFIT 2.1.0 release candidate 1.  
>> 
>> uimaFIT 2.1.0 is a bugfix release to uimaFIT 2.0.0. The reason that the 
>> minor version 
>> was increased instead of the bugfix version is that uima 2.1.0 requires Java 
>> 6 and
>> uses UIMA 2.6.0. Otherwise, uimaFIT 2.1.0 should serve as a drop-in 
>> replacement for
>> uimaFIT 2.0.0.
>> 
>> Changes:
>> 
>> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.1.0uimaFIT%20AND%20project%20%3D%20UIMA
>> 
>> The source and binary zip/tars are staged to
>> http://people.apache.org/%7Erec/uimafit-release-candidates/2.1.0-rc1/
>> 
>> The Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapacheuima-1022
>> 
>> The SVN tags are here:
>> https://svn.apache.org/repos/asf/uima/uimafit/tags/uimafit-2.1.0
>> 
>> See http://uima.apache.org/testing-builds.html for suggestions on how to test
>> release candidates.
>> 
>> Please vote on release:
>> 
>> [ ] +1 OK to release
>> [ ] 0   Don't care
>> [ ] -1 Not OK to release, because ...
>> 
>> Thanks.
>> 
>> -- Richard

Reply via email to