Still needing one more vote on this release. Anyone got time to check? On Sun, Dec 9, 2018 at 9:59 PM Paul King <pa...@asert.com.au> wrote:
> > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.16 release! This is a > maintenance release of the 2.4 branch and the last planned release for this > branch. > > This release includes 17 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12342996 > > Tag: > https://git1-us-west.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_16 > Tag commit id: f800b9f8ba85b5e328b545c4d8880dd47ed514f3 > > The artifacts to be voted on are located as follows (r31469). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/2.4.16/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/2.4.16/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.16. > > 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.16 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.16 because... > > Here is my vote: > > +1 (binding) > >