-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
signature on source-release: OK IssuesFixed: OK compare svn w/ source-release: OK. build from sources: Done on Windows, OK Eclipse artifacts are not signed causing a warning when installing into eclipse Install into Eclipse 4.15 - OK. Created a new project, looked at files. Release_notes and readme look fine. spot check maven artifacts: ok spot check licenses/ notice: ok I noticed that the eclipse artifacts are still not signed. This should be a straight-forward process, that would give "installers" more confidence that they're installing something official and not corrupted. It seems in this stage of the world (?!?) this would be a good thing to do... :-) [X] +1 OK to release - -Marshall Schor -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOn/mVSh3S1eNEDz+zHYv/c0Ez9YFAl6J4O8ACgkQzHYv/c0E z9bj9BAApycdpvKfjsUewPnc5QW9lvlo3Ve2xC2uF8Cg2zxILnUornDrIPI8lUsD /0G0vNpCML/QdWIRb42trwRkcGga6FbOYjdfGut+1wYTGV4dlsf/Tdo7F+Zajhds vB9cwle9B+jPIpQgEIC2wOjDopAcipS7+zdp8zkhkrym5asiTQiuzkwrUR7rUV9a 8o/7G0UzPtmdoikEFyXMpEb8QwrxhsxiTPCRdhmIfTGINBC8NuV4rHIFq/QZWvg0 7gPaaiyIwcBQQa6LnAVGzhII/gJtEDnxktCVxg1NfBVln0wyGEEGcXzDRtj61HkB XBwr805o/o+26htitdiQSzr4DEzldKPqEQymXcptyvIoy0SRZ5azOSIkINvSHhK2 S/blG5e2gWCTbjqBUCXDwxCc6ym1KdvV6JDkcCruOy5I0Iki/PrRtm+XuqpZ8bX7 VZWPORZKjWUioNV+8rmIrAMLaN3bBdOSpRdCUB38SsRDEGui6xSXRnuOMRa/Om7r P9YTvy2GYFi+OdKDpnYGLK/G+LwiB/FvGmAKw23j97AwA0BD5fARzwAIBu4c/Rim NHJYnBqCWO50AfjSMDN1b6P/hExXy0qZyMIOATjt56QQqZdP7zJy0I2w9oR2mfIJ bEEfVWFjLFA7fPytLH+MQ7aeMWAnpzPzJBJ5SlaUzpGXWWSIyTk= =jmDY -----END PGP SIGNATURE-----
