signatures OK (using Java 8) ran document analyzer from bin package, viewed results- OK installed into eclipse 490 - ran configurator, made type system, ran JCasGen - OK in Eclipse - imported examples folder from bin distr, ran documentAnalyzer, viewed results- OK compare source-release with tag - OK build from source - OK no change to license/notices vs 2.10.2 api-change-reports: OK issues-fixed report: OK
spot check licenses in staging repo: ok Note: It appears the Eclipse update site "publish" utility adds .sha1 and .md5 signatures; this might be needed by the Eclipse install-software facility, so I didn't remove them. Note: artifacts put in staging repo have .sha1 and md5 checksums added, probably by the "deploy" step? At this point, I think this is pending resolution of various rules in the Apache repo installation; I'm not planning to fix this (I think a fix would need to be a manual process, and it might cause some failure further upstream.) The artifacts in dist.apache.org/repos/dist/dev ... do not have the sha1 and md5 checksums, but they do have the sha512 checksum "signed" by the gpg one (due to pending rule fix in Apache repo installation). [X] +1 OK to release -Marshall
