Hurray! This will help reduce the grails build differences. +1 On Sat, Jul 19, 2025 at 7:43 AM Guillaume Laforge <glafo...@gmail.com> wrote:
> +1 (binding) > > On Sat, Jul 19, 2025 at 12:35 PM Paul King <pa...@asert.com.au> wrote: > >> >> Dear development community, >> >> I am happy to start the VOTE thread for a Groovy 4.0.28 release! >> >> This release includes 18 bug fixes/improvements as outlined in the >> changelog: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12355971 >> >> Tag: >> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_28 >> Tag commit id: 4acba1e45da1dbba2c39c7ba235cbc568dbeefa6 >> >> The artifacts to be voted on are located as follows (r78254). >> Source release: >> https://dist.apache.org/repos/dist/dev/groovy/4.0.28/sources >> Convenience binaries: >> https://dist.apache.org/repos/dist/dev/groovy/4.0.28/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.28. >> >> 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.28 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 4.0.28 because... >> >> Here is my vote: >> >> +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: @glafo...@uwyn.net <http://%40glafo...@uwyn.net/> > >
