Hi folks,

The vote has passed with SIX +1 binding votes and no other votes:

+1 paulk (binding)
+1 glaforge (binding)
+1 sbglasius (binding)
+1 blackdrag (binding)
+1 aalmiray (binding)
+1 emilles (binding)

I'll proceed with the next steps.

Cheers, Paul.

On Tue, Nov 5, 2024 at 10:44 AM Paul King <pa...@asert.com.au> wrote:
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-11 release!
>
> This release includes 47 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12355100
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_11
> Tag commit id: 68a39dfe622e9a404e1d353d53c5ff0efe37e5ca
>
> The artifacts to be voted on are located as follows (r72787).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-11/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-11/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 5.0.0-alpha-11.
>
> 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 5.0.0-alpha-11
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-11 because...
>
> Here is my vote:
>
> +1 paulk (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