Re-rolling for the same issue as the Groovy 3 re-roll. The 2.5.16 release was unaffected.
On Wed, Mar 2, 2022 at 3:33 PM Paul King <pa...@asert.com.au> wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.1 release! > > This release includes 40 bug fixes/improvements as outlined in the changelog: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12351284 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_1 > Tag commit id: 46976eec3670418873d69c0577ceda00b38fd754 > > The artifacts to be voted on are located as follows (r52805). > Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.1/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.1/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.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 4.0.1 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.1 because... > > Here is my vote: > > +1 (binding)
