- Checked binary signatures - OK - Built from source & checked signatures - OK - Ran MeetingDetector example on binary & source builds - OK - Tested service targeting of an already-deployed service on both builds - OK But using runRemoteAsyncAE with both -d and -TargetServiceId didn't work as the service was deployed with the default id --- not a blocker - Ran a large pipeline with both builds - OK - Issues fixed - OK - Spot checked uima-as docs - OK - Spot checked README, etc - OK
[X] +1 OK to release On Wed, Jan 31, 2018 at 11:34 AM, Marshall Schor <[email protected]> wrote: > signatures OK > compare svn tag with source release: OK > build from source OK > Install into Eclipse 4.7.0, create deployment descriptor OK > issues fixed: OK > > README: line 472 http link incorrect - goes to 1 specific issue. > - Not a blocker I think. > README: line 39 says Fixed dd2spring issues, but searching the issues for > "dd2spring" in Jira returns empty result? > - Not a blocker I think. > README.uimaj.txt has a link to issues fixed, which goes (of course!) to the > uima-as issues fixed. > - Not a blocker I think. > > License / notice : no change from rc2 > > ran quick-start tests OK (but broker window reported at end 2 messages of > Transport Connection to: tcp://127.0.0.1:65064 failed: > java.net.SocketException: > Connection reset - which is expected. > > [X] +1 OK to release > > -Marshall Schor > >
