+1 (binding)

On Mon, Feb 4, 2019 at 4:31 AM Andres Almiray <aalmi...@gmail.com> wrote:

> +1 (binding)
>
> Sent from my primitive tricorder
>
> On Feb 3, 2019, at 23:52, Remko Popma <remko.po...@gmail.com> wrote:
>
> +1
>
> Remko.
>
> On Feb 4, 2019, at 7:31, John Wagenleitner <john.wagenleit...@gmail.com>
> wrote:
>
> +1 (binding)
>
> On Fri, Feb 1, 2019 at 3:04 AM Paul King <pa...@asert.com.au> wrote:
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 2.5.6 release!
>>
>> This release includes 24 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12344751
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_6
>> Tag commit id: f296142df4b0f0da30e36502f900c0a56929af65
>>
>> The artifacts to be voted on are located as follows (r32292).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/2.5.6/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/2.5.6/distribution
>>
>> Release artifacts are signed with a key from the following file:
>> https://dist.apache.org/repos/dist/dev/groovy/KEYS
>>
>> Please vote on releasing this package as Apache Groovy 2.5.6.
>>
>> 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 2.5.6
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.5.6 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