+1 (binding)

On Wed, Mar 2, 2022 at 8:34 AM Søren Berg Glasius <soe...@glasius.dk> wrote:

> +1 (not binding)
>
> Best regards / Med venlig hilsen,
> Søren Berg Glasius
>
> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
> Mobile: +45 40 44 91 88, Skype: sbglasius
> --- Press ESC once to quit - twice to save the changes.
>
>
> Den ons. 2. mar. 2022 kl. 05.41 skrev Paul King <pa...@asert.com.au>:
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 3.0.10 release!
>>
>> This release includes 93 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12350584
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_10
>> Tag commit id: cde25a15c16eff4fc7f99b3c8706f5750a118305
>>
>> The artifacts to be voted on are located as follows (r52802).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.10/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.10/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.10.
>>
>> 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.10
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 3.0.10 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>

Reply via email to