The vote has passed with FOUR +1 binding votes and no other votes.

I'll proceed with the next steps.

Cheers, Paul.

On Wed, Jan 17, 2024 at 1:05 AM Jochen Theodorou <blackd...@gmx.org> wrote:
>
> +1
>
> Am 16.01.24 um 04:26 schrieb Paul King:
> > Dear development community,
> >
> > I am happy to start the VOTE thread for a Groovy 4.0.18 release!
> >
> > This release includes 16 bug fixes/improvements as outlined in the 
> > changelog:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12354066
> >
> > Tag: 
> > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_18
> > Tag commit id: c17afaaf3984624e98519fcd397439d152f55b10
> >
> > The artifacts to be voted on are located as follows (r66628).
> > Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.18/sources
> > Convenience binaries:
> > https://dist.apache.org/repos/dist/dev/groovy/4.0.18/distribution
> >
> > Release artifacts are signed with a key from the following file:
> > https://dist.apache.org/repos/dist/release/groovy/KEYS
> >
> > Please vote on releasing this package as Apache Groovy 4.0.18.
> >
> > 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 4.0.18
> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 4.0.18 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>
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Reply via email to