You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by Richard Eckart de Castilho <re...@apache.org> on 2019/04/11 12:09:39 UTC

[VOTE] Release uimaFIT 3.0.0 rc 2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I've posted the uimaFIT 3.0.0 release candidate 2.

uimaFIT 3.0.0 is major feature release which makes uimaFIT
compatible with UIMAJ v3. It includes incompatible API changes
as well as new features and bug fixes.

Changes since RC1:

- - Restored isMultiValuedFeature() signature which was unintentionally removed
- - Depend on UIMAJ Core 3.0.2
- - Use UIMA parent POM version 12
- - Generate API reports comparing against uimaFIT 2.4.0
- - Properly configure logging in tests and examples
- - Removed redundant declaration of Java target version in benchmark module
- - Switched from commons-lang to commons-lang3
- - Upgraded Spring dependency
- - Updated NOTICE and LICENSE files of distribution packages accordingly
- - Run rat check on every build
- - Added "api-change-report.html" to project and to assembly
- - Added selectSingleFS method to CasUtil
- - Elaborated migration guide from 2.x to 3.x
- - Point to GitHub repo for sources in README

Changes:
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.0.0uimaFIT%20AND%20project%20%3D%20UIMA

The source and binary tar/zips are here:
https://dist.apache.org/repos/dist/dev/uima/uimafit/3.0.0-rc2/

The Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapacheuima-1230

The GIT tag is here:
https://github.com/apache/uima-uimafit/tree/uimafit-3.0.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
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEPY2MKJLmMo4NDQCrO8wPPFbjAA4FAlyvLmhfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNE
OEQ4QzI4OTJFNjMyOEUwRDBEMDBBQjNCQ0MwRjNDNTZFMzAwMEUACgkQO8wPPFbj
AA4l0g//fQ91Ev+srK3W4Dus/L6eGmlDp1busP1sqNtxtusjNPy8pIAoFvbh+7jp
wb/TJg5vOkTEAbZc/BKhLjghbY6aHVWTU5wuf4e29GJLtnpCNG/timYm5foHcsGx
uXuXXfFUW3xSAMNRJKQY5dxizZ70N8vHQ3GtlM7eeeuDLtqOJ6iRdnRFjOdWxELQ
tb9Z1BVTWQQ7beXfedfVoC7TqhRpYY9anc6OqrkJBgP4fuMvNCV0JT2x5vv43iUa
ZAbaQsAz9tQYtyv8uUVTJlNEcqZ/9ZHpZCBHa089OY6Fg607IwbxLrJalHMT7MKw
EH//JgSnsDnsb/ycMdl5bUAZL342ltpqgduMfD1BgYhwYoYnXCz7gyBT4CE/UxT7
38VRNSXPzrA/+O9iNHGTqoShu718DAmeflPG4F+ZifU0dID6SBqyd7P2hGSFz9Y9
6dv1Arc2Jhk2J3X3FnPkO5B2s3NixDr+GN1yoX5GZgJxIqFb1wgX5XR+ZdnqXViZ
/HEoQgsts+Q2G3Gn5mv1c4/tzIrdv8X4uIl5UvhUIBjnCG5aAe36V6sakmiFopgr
9hxtfch86ljGONT9ZShQeuHTxS8OcPRlLSbwTdz9xahldHXVt1k4qAnHJ0hvQ9lE
k3GRXm0Cm4uzTdCBUQf7v5kjAHi7byqu4y15i9LYD70SUyS5mL8=
=bCFM
-----END PGP SIGNATURE-----

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <ms...@schor.com>.

:-)

On 4/12/2019 5:50 PM, Richard Eckart de Castilho wrote:
> On 12. Apr 2019, at 19:46, Marshall Schor <ms...@schor.com> wrote:
>> Is this set of conventions (3.0.x and master branches being "protected", and how
>> to make releases) documented (in some obvious spot :-) )?
> Not really - this is the first time I have to do it this way because
> INFRA manages the repo and I don't have admin permission. So I'm basically
> making things up as I'm going and hope it works out. 
>
> But yes, once it figures, I should document it...
>
> -- Richard

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Richard Eckart de Castilho <re...@apache.org>.

On 12. Apr 2019, at 19:46, Marshall Schor <ms...@schor.com> wrote:
> 
> Is this set of conventions (3.0.x and master branches being "protected", and how
> to make releases) documented (in some obvious spot :-) )?

Not really - this is the first time I have to do it this way because
INFRA manages the repo and I don't have admin permission. So I'm basically
making things up as I'm going and hope it works out. 

But yes, once it figures, I should document it...

-- Richard

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <ms...@schor.com>.

yes, makes sense.

Is this set of conventions (3.0.x and master branches being "protected", and how
to make releases) documented (in some obvious spot :-) )?

-Marshall

On 4/12/2019 11:52 AM, Richard Eckart de Castilho wrote:
> On 12. Apr 2019, at 16:53, Marshall Schor <ms...@schor.com> wrote:
>> Do you expect the MASTER branch to not be tracking the lastest updates, in your
>> particular GIT workflow?  If so, can you briefly describe your workflow?
> The master branch of the uimaFIT github repo tracks the 2.5.x line at the moment.
> It will be updated when (if) a 2.5.0 release is prepared.
>
> The 3.0.x branch tracks the UIMAv3 developments in general.
>
> The "release/3.0.0" branch tracks the actual release and has a few minor changes which the
> 3.0.x branch does not yet have. Once the release is approved, the "release/3.0.0" branch
> is merged into the 3.0.x branch to bring it up-to-date.
>
> Both the "master" and "3.0.x" branches are protected, so I cannot push to them directly.
> That is why I prepare the release on the "release/3.0.0" branch.
>
> Makes sense?
>
> -- Richard

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Richard Eckart de Castilho <re...@apache.org>.

On 12. Apr 2019, at 16:53, Marshall Schor <ms...@schor.com> wrote:
> 
> Do you expect the MASTER branch to not be tracking the lastest updates, in your
> particular GIT workflow?  If so, can you briefly describe your workflow?

The master branch of the uimaFIT github repo tracks the 2.5.x line at the moment.
It will be updated when (if) a 2.5.0 release is prepared.

The 3.0.x branch tracks the UIMAv3 developments in general.

The "release/3.0.0" branch tracks the actual release and has a few minor changes which the
3.0.x branch does not yet have. Once the release is approved, the "release/3.0.0" branch
is merged into the 3.0.x branch to bring it up-to-date.

Both the "master" and "3.0.x" branches are protected, so I cannot push to them directly.
That is why I prepare the release on the "release/3.0.0" branch.

Makes sense?

-- Richard

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <ms...@schor.com>.

Working on testing.  I have a general git question:

I cloned the repo pointed to by the url for the tag, using the button on web
page "clone or download", using the URL provided there: 
https://github.com/apache/uima-uimafit.git

This cloned the repo, and all the tags, and checked out some version (master?). 

This version has lots of miscompares with the source-release.  For example, the
NOTICE file has a copyright date ending in 2017.

I fixed this by doing a git checkout of tag uimafit-3.0.0; the compare is
correct using that.

I can confirm that the MASTER branch (at https://github.com/apache/uima-uimafit
) has a NOTICE file that hasn't been updated in 2 years - which explains why it
still has the 2017 copyright date.

Do you expect the MASTER branch to not be tracking the lastest updates, in your
particular GIT workflow?  If so, can you briefly describe your workflow?

Thanks.  (Not an issue for release).  -Marshall

[VOTE][RESULT] Release uimaFIT 3.0.0 rc 2

Posted by Richard Eckart de Castilho <re...@apache.org>.

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Peter Klügl <pe...@averbis.com>.

maven build svn-tag - OK
maven build source-release - OK
spot checked jira report/readme/notice/license OK
spot checked sig/checksum - OK
build ruta-core v3 - FAILED

The code base required some changes. Then, still three tests failed,
however, caused by the uimaj version. I need to take a closer look, but
this is no blocker for the rc.


[X] +1 OK to release


Best,


Peter


Am 11.04.2019 um 14:09 schrieb Richard Eckart de Castilho:
> Hi,
>
> I've posted the uimaFIT 3.0.0 release candidate 2.
>
> uimaFIT 3.0.0 is major feature release which makes uimaFIT
> compatible with UIMAJ v3. It includes incompatible API changes
> as well as new features and bug fixes.
>
> Changes since RC1:
>
> - Restored isMultiValuedFeature() signature which was unintentionally
> removed
> - Depend on UIMAJ Core 3.0.2
> - Use UIMA parent POM version 12
> - Generate API reports comparing against uimaFIT 2.4.0
> - Properly configure logging in tests and examples
> - Removed redundant declaration of Java target version in benchmark module
> - Switched from commons-lang to commons-lang3
> - Upgraded Spring dependency
> - Updated NOTICE and LICENSE files of distribution packages accordingly
> - Run rat check on every build
> - Added "api-change-report.html" to project and to assembly
> - Added selectSingleFS method to CasUtil
> - Elaborated migration guide from 2.x to 3.x
> - Point to GitHub repo for sources in README
>
> Changes:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%203.0.0uimaFIT%20AND%20project%20%3D%20UIMA
>
> The source and binary tar/zips are here:
> https://dist.apache.org/repos/dist/dev/uima/uimafit/3.0.0-rc2/
>
> The Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapacheuima-1230
>
> The GIT tag is here:
> https://github.com/apache/uima-uimafit/tree/uimafit-3.0.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
> --
Dr. Peter Klügl
R&D Text Mining/Machine Learning

Averbis GmbH
Salzstr. 15
79098 Freiburg
Germany

Fon: +49 761 708 394 0
Fax: +49 761 708 394 10
Email: peter.kluegl@averbis.com
Web: https://averbis.com

Headquarters: Freiburg im Breisgau
Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080
Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Richard Eckart de Castilho <re...@apache.org>.

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <ms...@schor.com>.

found the problem.  Had to cd to the uimafit-parent project and install that
first, to update some things from the previous 3.0.0 release candidate 1.

-Marshall


On 4/12/2019 11:14 AM, Marshall Schor wrote:
> When building from sources using maven 3.6.0, I get immediately POM errors
> saying the "version" is missing for some dependencies.
>
> One example is org.apache.commons:commons-lang3  
>
> Indeed, looking at the pom (in the uimafit-core project) it is missing a version.
>
> Obviously you got it to build; I wonder what the difference is?
>
> -Marshall
>
>

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <ms...@schor.com>.

When building from sources using maven 3.6.0, I get immediately POM errors
saying the "version" is missing for some dependencies.

One example is org.apache.commons:commons-lang3  

Indeed, looking at the pom (in the uimafit-core project) it is missing a version.

Obviously you got it to build; I wonder what the difference is?

-Marshall

Re: [VOTE] Release uimaFIT 3.0.0 rc 2

Posted by Marshall Schor <sc...@apache.org>.