+1 Looks good from what I've tried. On Mon, May 28, 2018 at 5:51 AM, John Wagenleitner < john.wagenleit...@gmail.com> wrote:
> +1 (binding) > > > On Sat, May 26, 2018 at 8:29 PM Paul King <pa...@asert.com.au> wrote: > >> >> Dear development community, >> >> I am happy to start the VOTE thread for a Groovy 2.5.0 release! >> >> This release includes 12 bug fixes/improvements as outlined in the >> changelog: >> https://issues.apache.org/jira/secure/ReleaseNote.jspa? >> projectId=12318123&version=12343341 >> >> Tag: https://git1-us-west.apache.org/repos/asf?p=groovy.git;a= >> tag;h=refs/tags/GROOVY_2_5_0 >> Tag commit id: cfea02483ef46c89eae66d4af932a725574edc4d >> >> The artifacts to be voted on are located as follows (r27123). >> Source release: https://dist.apache.org/repos/ >> dist/dev/groovy/2.5.0/sources >> Convenience binaries: https://dist.apache.org/repos/ >> dist/dev/groovy/2.5.0/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.5.0. >> >> 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.5.0 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 2.5.0 because... >> >> Here is my vote: >> >> +1 (binding) >> >>
