On Tue, Mar 14, 2017 at 4:17 PM, Guillaume Laforge <firstname.lastname@example.org> wrote:
> This time, following instructions, using the proper wrapper, all is fine on
> my side :-)
> On Tue, Mar 14, 2017 at 4:05 PM, Paul King <email@example.com> wrote:
>> Dear community,
>> I am happy to (re)start the VOTE thread for a Groovy 2.4.10 release!
>> This release has the problematic stricter method checking
>> (GROOVY-6792) disabled by default but it can be enabled with a system
>> property. Thanks John for spotting the potential problem. Even though
>> I think it would have had minor impact I think it was worth re-cutting
>> the release.
>> This release includes 11 bug fixes/improvements as outlined in the
jira/secure/ReleaseNote.jspa? projectId=12318123&version= 12339743
>> Tag commit id: 6ecdb9de12ffcdd1b0937fd2c15a30
>> The artifacts to be voted on are located as follows (r18737).
>> Source release:
>> Convenience binaries:
>> Release artifacts are signed with a key from the following file:
>> Please vote on releasing this package as Apache Groovy 2.4.10.
>> 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.4.10
>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.4.10 because...
>> Here is my vote:
>> +1 (binding)
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+