+1 (binding) *Guillaume Laforge* Apache Groovy committer Developer Advocate @ Google Cloud <https://cloud.google.com/>
- Blog: glaforge.dev - X: @glaforge <http://twitter.com/glaforge> - Bluesky: @glaforge.dev <https://bsky.app/profile/glaforge.dev> - Mastodon: @[email protected] <http://%[email protected]/> Le sam. 1 août 2026, 05:04, Paul King <[email protected]> a écrit : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 6.0.0-beta-1 release! > > This release includes 88 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12357232 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_6_0_0_BETA_1 > Tag commit id: 413e8f5dc72b0c83519c6abb656c4bb00da9bf8d > > The artifacts to be voted on are located as follows (r86410). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/6.0.0-beta-1/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/6.0.0-beta-1/distribution > Temp artifacts: > https://repository.apache.org/content/repositories/orgapachegroovy-1115 > > 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 6.0.0-beta-1. > > 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 6.0.0-beta-1 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 6.0.0-beta-1 because... > > Here is my vote: > > +1 (binding) > > GroovyPolicyMSP assessment: > Assessed Groovy 6.0.0-beta-1 RC artifacts against ASF release policy: > everything passed (signatures, checksums, LICENSE/NOTICE, source > hygiene, full Maven staging sweep) > > verify.sh results: > ✅ Source Distribution Verified > ✅ Binary Distribution Verified > ✅ Docs Distribution Verified > ✅ SDK Distribution Verified > ✅ RAT passed > ✅✅✅ Automatic verification finished. >
