Hi, so... after a long while...
> On 25. Jan 2019, at 00:17, Marshall Schor <[email protected]> wrote: > > API compare: the old version is 2.1.0 - should it be 2.4.0? (not a blocker) Addressed by UIMA-6005 > checked api conformance - discussed in another note. (not a blocker here) Addressed by UIMA-6006 - the isMultiValuedFeature signature has been restored. However, the changes to the return values in CasUtil, JCasUtil, and FSCollectionFactory remain. I am using the major version jump to get rid of some sins of the past. > saw that tests were running with NOP logger - not a blocker - because I don't > think logging is being used. (not a blocker) Addressed by UIMA-6004 > It appears that two issues fixed in 3.0.0 didn't make it to the fixed list: > https://issues.apache.org/jira/browse/UIMA-5348 > https://issues.apache.org/jira/browse/UIMA-5810 > (not a blocker ? but may be indicative of some problem in the release > process?) These had the wrong "component". Added the "uimaFIT" component to both. > It appears that the dependency declared in uimafit-core for "commons-logging" > isn't needed? (not a blocker) Addressed by UIMA-6009 - the Maven dependency plugin is now used to ensure that there are not too few and not too many dependencies. > NOTICE files have 2016 or 2017 (depending on binary or source-release) as the > end copyright date, probably should say 2019, or be left off. (not a blocker) Addressed by https://github.com/apache/uima-uimafit/pull/56 (no Jira) > in the source-release, the file api-change-report.html (which aggregates the 3 > generated ones) is missing (not a blocker) Addressed by UIMA-6012 > There's a new project, "benchmark", which isn't described in the docs? (not a > blocker) It is not meant for user consumption and not deployed to Maven Central. So this should (hopefully) tackle it. While at it, I have made a few additional improvements. Now I'll go on to prepare the next RC. Cheers, -- Richard
