The api change report is configured to report changes between 2.3.1 and 2.1.0. (looking at uimafit-core)
I would have expected it to be configured to compare to 2.2.0 or 2.3.0 (the latter would report no change I suspect). Any reason for picking 2.1.0 or is it just misconfigured? -Marshall On 5/26/2017 1:35 PM, Richard Eckart de Castilho wrote: > Hi all, > > this is a bugfix release: > > - Fixed bug: indexCovered should not return reference annotation > > Staging repository: > > https://repository.apache.org/content/repositories/orgapacheuima-1143 > > SVN tag: > > https://svn.apache.org/repos/asf/uima/uimafit/tags/uimafit-2.3.1 > > Release artifacts are here: > > https://dist.apache.org/repos/dist/dev/uima/uimafit-2.3.1-rc1/ > > Overall 1 issues have been resolved for this release. > They can be found in the jira-report.html. > > ... and here: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%202.3.1uimaFIT%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC > > Please vote on release: > > [ ] +1 OK to release > [ ] 0 Don't care > [ ] -1 Not OK to release, because ... > > Cheers, > > -- Richard
