Thanks everyone for voting. The vote has passed with five +1 votes from PMC
members and two additional +1 votes. I'll proceed with next steps.
On Wed, Feb 21, 2018 at 11:58 PM, Jochen Theodorou <blackd...@gmx.org>
> Am 21.02.2018 um 14:56 schrieb John Wagenleitner:
>> +1 (binding)
>> On Feb 19, 2018 9:36 PM, "Paul King" <pa...@asert.com.au <mailto:
>> pa...@asert.com.au>> wrote:
>> Dear development community,
>> I am happy to start the VOTE thread for a Groovy 2.5.0-beta-3 release!
>> There are still a few things we plan to work on before the final
>> release but
>> we anticipate this will be the last beta for the 2.5.0 release
>> train. So we'd greatly
>> appreciate as much testing as possible before we get the first RC
>> ready shortly.
>> This release includes 39 bug fixes/improvements as outlined in the
>> Tag commit id: 1f5ba16e86ebc2ed9146aab13304e316c812a838
>> The artifacts to be voted on are located as follows (r25155).
>> Source release:
>> Convenience binaries:
>> (If building from the source zip, the bootstrapping details changed
>> make sure to read the README.adoc file to brush up on the details if
>> Release artifacts are signed with a key from the following file:
>> Please vote on releasing this package as Apache Groovy 2.5.0-beta-3.
>> Reminder on ASF release approval requirements for PMC members:
>> Hints on validating checksums/signatures (but replace md5sum with
>> 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.0-beta-3
>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.5.0-beta-3 because...
>> Here is my vote:
>> +1 (binding)