Hi Paul, Same tests as usual. Downloaded, built from source, ran a few scripts without any problem. Everything fine on my side.
+1 (binding) Guillaume On Sat, Feb 24, 2018 at 12:46 PM, Paul King <pa...@asert.com.au> wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.14 release! > > This release includes 14 bug fixes/improvements as outlined in the > changelog: > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12318123&version=12342217 > > Tag: https://git1-us-west.apache.org/repos/asf?p=groovy.git;a= > tag;h=refs/tags/GROOVY_2_4_14 > Tag commit id: c767bce7b97813d988a87e9c86439859056711d8 > > The artifacts to be voted on are located as follows (r25261). > Source release: https://dist.apache.org/repos/ > dist/dev/groovy/2.4.14/sources > Convenience binaries: https://dist.apache.org/repos/ > dist/dev/groovy/2.4.14/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/dev/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 2.4.14. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > The vote is open for the next 72 hours and passes if a majority of at > least three +1 PMC votes are cast. > > [ ] +1 Release Apache Groovy 2.4.14 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.14 because... > > Here is my vote: > > +1 (binding) > > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>
