+1 Remko. On Sat, Feb 29, 2020 at 9:33 PM Paul King <pa...@asert.com.au> wrote:
> > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.19 release! > We weren't planning another 2.4.X release and there aren't many changes > but a downstream dependency bug is impacting numerous users stuck on Groovy > 2.4. So this should fix things for impacted users. > > This release includes 4 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12346771 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_19 > Tag commit id: 10931efeab0b6d9f3cb0335ee3e647b6d7abfa78 > > The artifacts to be voted on are located as follows (r38334). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/2.4.19/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/2.4.19/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.19. > > 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.19 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.19 because... > > Here is my vote: > > +1 (binding) > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_-8442891159981306496_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >