+1 (binding) On Sun, May 29, 2022 at 4:50 AM Paul King <pa...@asert.com.au> wrote:
> Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.11 release! > > This release includes 65 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12351420 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_11 > Tag commit id: 47bc9214e9d0f31ea5f66846be6d23a5d3f10031 > > The artifacts to be voted on are located as follows (r54774). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.11/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.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 3.0.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 3.0.11 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.11 because... > > Here is my vote: > > +1 (binding) > -- Guillaume Laforge Apache Groovy committer Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Twitter: @glaforge <http://twitter.com/glaforge>
