Re: [VOTE] Release Apache Groovy 4.0.21

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sat, Apr 6, 2024 at 6:16 PM Guillaume Laforge  wrote:

> +1 (binding)
>
> Le sam. 6 avr. 2024, 14:48,  a écrit :
>
>> +1
>>
>> -Original Message-
>> From: Paul King 
>> Sent: Saturday, April 6, 2024 12:33 AM
>> To: Groovy_Developers 
>> Subject: [VOTE] Release Apache Groovy 4.0.21
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 4.0.21 release!
>>
>> This release includes 8 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354415
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_21
>> Tag commit id: 9ca628fdf0871ac299b464867b1329de77a72ef4
>>
>> The artifacts to be voted on are located as follows (r68338).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.21/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.21/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 4.0.21.
>>
>> 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 4.0.21
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok [ ]
>> -1 Do not release Apache Groovy 4.0.21 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>>

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-8

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sat, Apr 6, 2024 at 6:16 PM Guillaume Laforge  wrote:

> +1 (binding)
>
> Le sam. 6 avr. 2024, 13:18, Paul King  a écrit :
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-8 release!
>>
>> This release includes 15 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354408
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_8
>> Tag commit id: f6221ee780bfb2f84fb197da2c13387c4e93a019
>>
>> The artifacts to be voted on are located as follows (r68337).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-8/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-8/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 5.0.0-alpha-8.
>>
>> 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 5.0.0-alpha-8
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-8 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>

Re: [VOTE] Release Apache Groovy 4.0.20

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 11 Mar 2024, at 10:17, Jochen Theodorou  wrote:
> 
> +1
> 
>> On 11.03.24 01:16, Paul King wrote:
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 4.0.20 release!
>> 
>> This release includes 7 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354376
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_20
>> Tag commit id: fb36c6a20b99e388abbe0348c8007f9636ca449a
>> 
>> The artifacts to be voted on are located as follows (r67870).
>> Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.20/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.20/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 4.0.20.
>> 
>> 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 4.0.20
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.20 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
>> 
>> 
>> Virus-free.www.avast.com
>> 
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-7

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 11 Mar 2024, at 10:18, Jochen Theodorou  wrote:
> 
> +1
> 
>> On 11.03.24 00:04, Paul King wrote:
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-7 release!
>> 
>> This release includes 12 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354374
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_7
>> Tag commit id: 6dad260e0702e5c983481502cc8fcb97f4be21e0
>> 
>> The artifacts to be voted on are located as follows (r67868).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-7/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-7/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 5.0.0-alpha-7.
>> 
>> 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 5.0.0-alpha-7
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-7 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
>> 
>> 
>> Virus-free.www.avast.com
>> 
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 

Re: [VOTE] Release Apache Groovy 3.0.21

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Feb 2024, at 12:10, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.21 release!
> 
> This release includes 17 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354073
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_21
> Tag commit id: c4681c558ccc0644e217beb3ca7cd641fbc2533d
> 
> The artifacts to be voted on are located as follows (r67600).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.21/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.21/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.21.
> 
> 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.21
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.21 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 
> 
> Virus-free.www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: [VOTE] Release Apache Groovy 4.0.19

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Feb 2024, at 11:43, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 4.0.19 release!
> 
> This release includes 18 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354149
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_19
> Tag commit id: 7d25a39ae4c26f38b86b181c98e079a40e1d787e
> 
> The artifacts to be voted on are located as follows (r67599).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.19/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.19/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 4.0.19.
> 
> 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 4.0.19
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.19 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-6

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 27 Feb 2024, at 10:18, Guillaume Laforge  wrote:+1 (binding)On Tue, Feb 27, 2024 at 8:48 AM Paul King  wrote:Dear development community,

I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-6 release!

This release includes 29 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354153

Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_6
Tag commit id: 5769bc66c28b0ca5e9aedeb8bdef24723e981401

The artifacts to be voted on are located as follows (r67592).
Source release:
https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-6/sources
Convenience binaries:
https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-6/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 5.0.0-alpha-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 5.0.0-alpha-6
[ ]  0 I don't have a strong opinion about this, but I assume it's ok
[ ] -1 Do not release Apache Groovy 5.0.0-alpha-6 because...

Here is my vote:

+1 (binding)


Virus-free.www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-5

[Andres Almiray]

+1 (binding)

On Tue, Jan 16, 2024 at 5:56 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
>
> On Tue, Jan 16, 2024 at 12:47 PM Paul King  wrote:
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-5 release!
>>
>> This release includes 21 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354072
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_5
>> Tag commit id: edcba8e9aec60c8f8657335f686e3683f7ee2857
>>
>> The artifacts to be voted on are located as follows (r66637).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-5/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-5/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 5.0.0-alpha-5.
>>
>> 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 5.0.0-alpha-5
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-5 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> Virus-free.www.avast.com
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud 
>
>- Blog: glaforge.dev
>- Twitter: @glaforge 
>- Mastodon: @glafo...@uwyn.net 
>
>

Re: [VOTE] Release Apache Groovy 4.0.18

[Andres Almiray]

+1 (binding)



On Tue, Jan 16, 2024 at 1:33 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> Le mar. 16 janv. 2024, 04:26, Paul King  a écrit :
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 4.0.18 release!
>>
>> This release includes 16 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12354066
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_18
>> Tag commit id: c17afaaf3984624e98519fcd397439d152f55b10
>>
>> The artifacts to be voted on are located as follows (r66628).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.18/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.18/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 4.0.18.
>>
>> 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 4.0.18
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.18 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> Virus-free.www.avast.com
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>

Re: [VOTE] Release Apache Groovy 4.0.17

[Andres Almiray]

+1 (binding)

On Mon, Dec 18, 2023 at 8:28 PM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.17 release!
>
> This release includes 8 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353979
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_17
> Tag commit id: 0bd637ff3a7bf917fe5edb907f331861c0df8a84
>
> The artifacts to be voted on are located as follows (r66156).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.17/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.17/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 4.0.17.
>
> 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 4.0.17
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.17 because...
>
> Here is my vote:
>
> +1 (binding)
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-4

[Andres Almiray]

+1 (binding)

On Mon, Dec 18, 2023 at 7:10 PM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-4 release!
>
> This release includes 16 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353967
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_4
> Tag commit id: 433daecc3942257fc33c159765b25bb3aa77d3ed
>
> The artifacts to be voted on are located as follows (r66155).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-4/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-4/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 5.0.0-alpha-4.
>
> 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 5.0.0-alpha-4
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-4 because...
>
> Here is my vote:
>
> +1 (binding)
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 3.0.20

[Andres Almiray]

+1 (binding)



On Mon, Dec 18, 2023 at 8:54 PM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.20 release!
>
> This release includes 59 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353572
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_20
> Tag commit id: 6ad73a654d11db5abd383dde16f8587954c07dd4
>
> The artifacts to be voted on are located as follows (r66157).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.20/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.20/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.20.
>
> 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.20
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.20 because...
>
> Here is my vote:
>
> +1 (binding)
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 4.0.16

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 27 Nov 2023, at 8:42, Guillaume Laforge  wrote:+1 (binding)On Mon, Nov 27, 2023 at 8:31 AM Søren Berg Glasius  wrote:+1 (not binding)Den søn. 26. nov. 2023 kl. 21.58 skrev Paul King :Dear development community,

I am happy to start the VOTE thread for a Groovy 4.0.16 release!

This release includes 25 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353637

Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_16
Tag commit id: 12918f361bf20795cc2a8a1bf736a5b440146326

The artifacts to be voted on are located as follows (r65550).
Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.16/sources
Convenience binaries:
https://dist.apache.org/repos/dist/dev/groovy/4.0.16/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 4.0.16.

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 4.0.16
[ ]  0 I don't have a strong opinion about this, but I assume it's ok
[ ] -1 Do not release Apache Groovy 4.0.16 because...

Here is my vote:

+1 (binding)


Virus-free.www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-- Med venlig hilsen,Søren Berg GlasiusHedevej 1, Gl. Rye, 8680 RyMobile: +45 40 44 91 88--- Press ESC once to quit - twice to save the changes.
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-3

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Nov 2023, at 15:02, Daniel Sun  wrote:
> 
> groovyConsole and groovySh work well.
> 
> +1 (binding)
> 
> Cheers,
> Daniel Sun
> 
>> On 2023/11/26 21:54:52 Paul King wrote:
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-3 release!
>> 
>> This release includes 47 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353636
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_3
>> Tag commit id: f56e682eab977a8b4f9a5183e54443d855614b91
>> 
>> The artifacts to be voted on are located as follows (r65554).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-3/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-3/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 5.0.0-alpha-3.
>> 
>> 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 5.0.0-alpha-3
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-3 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
>> 
>> 
>> Virus-free.www.avast.com
>> 
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> 

Re: [VOTE] Release Apache Groovy 4.0.15

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Sep 11, 2023 at 11:44 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Mon, Sep 11, 2023 at 11:24 AM Paul King  wrote:
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 4.0.15 release!
>>
>> This release includes 12 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353571
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_15
>> Tag commit id: f821c4627c197b6332e1d0e200681f3ae411df83
>>
>> The artifacts to be voted on are located as follows (r63911).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.15/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.15/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 4.0.15.
>>
>> 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 4.0.15
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.15 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> Virus-free.www.avast.com
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud 
>
>- Blog: glaforge.dev
>- Twitter: @glaforge 
>- Mastodon: @glafo...@uwyn.net 
>
>

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-2

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 11 Sep 2023, at 10:21, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-2 release!
> 
> This release includes 20 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353570
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_2
> Tag commit id: 50b6e95748b76f272e6e865c04988388a1277974
> 
> The artifacts to be voted on are located as follows (r63907).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-2/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-2/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 5.0.0-alpha-2.
> 
> 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 5.0.0-alpha-2
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-2 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 
> 
> Virus-free.www.avast.com
> 
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: [VOTE] Release Apache Groovy 5.0.0-alpha-1

[Andres Almiray]

+1 (binding)

Is there a list of breaking changes for 5.x?

On Sat, Aug 19, 2023 at 4:21 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-1 release!
>
> NOTE: We are not feature complete for Groovy 5. In the release notes,
> I will make it clear that this is an alpha release, not recommended for
> production use and subject to change. But I think we need to start getting
> feedback on the parts that are ready and having a release will help with
> that.
>
> This release includes 119 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351227
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_1
> Tag commit id: cbd5a526a7af9375858c8967adc1e32555cb91f7
>
> The artifacts to be voted on are located as follows (r63508).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-1/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-1/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 5.0.0-alpha-1.
>
> 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 5.0.0-alpha-1
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 5.0.0-alpha-1 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 4.0.14

[Andres Almiray]

+1 (binding)

On Sat, Aug 19, 2023 at 5:18 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.14 release!
>
> This release includes 15 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353386
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_14
> Tag commit id: 034b8f90052752c978c5454cc3b17b163c68ffec
>
> The artifacts to be voted on are located as follows (r63509).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.14/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.14/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 4.0.14.
>
> 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 4.0.14
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.14 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 3.0.19

[Andres Almiray]

+1 (binding)

On Sat, Aug 19, 2023 at 6:51 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.19 release!
>
> This release includes 7 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353387
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_19
> Tag commit id: 1040cabcefe8e0776ca2d87e7a3f0ee2840dbf68
>
> The artifacts to be voted on are located as follows (r63510).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.19/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.19/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.19.
>
> 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.19
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.19 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 2.5.23

[Andres Almiray]

+1 (binding)


On Sat, Aug 19, 2023 at 7:50 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.23 release!
>
> This release includes 2 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353077
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_23
> Tag commit id: a8f3b116afd969be3f06b1807371d976462d6a2c
>
> The artifacts to be voted on are located as follows (r63511).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.23/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.23/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 2.5.23.
>
> 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.23
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.23 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 4.0.13

[Andres Almiray]

+1 (binding)

On Mon, Jun 26, 2023 at 10:29 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Mon, Jun 26, 2023 at 10:15 AM Jochen Theodorou 
> wrote:
>
>> +1
>>
>> Am 26.06.23 um 08:53 schrieb Søren Berg Glasius:
>> > +1 (not binding)
>> >
>> > Med venlig hilsen,
>> > Søren Berg Glasius
>> >
>> > Hedevej 1, Gl. Rye, 8680 Ry
>> > Mobile: +45 40 44 91 88
>> > --- Press ESC once to quit - twice to save the changes.
>> >
>> >
>> > Den man. 26. jun. 2023 kl. 08.32 skrev Paul King > > >:
>> >
>> >
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 4.0.13 release!
>> >
>> > This release includes 25 bug fixes/improvements as outlined in the
>> > changelog:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353213
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353213
>> >
>> >
>> > Tag:
>> >
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_13
>> <
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_13
>> >
>> > Tag commit id: c8eaf830d481572e1cd668b77c2fb2b444ce8f87
>> >
>> > The artifacts to be voted on are located as follows (r62641).
>> > Source release:
>> > https://dist.apache.org/repos/dist/dev/groovy/4.0.13/sources
>> > 
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/4.0.13/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 4.0.13.
>> >
>> > 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 4.0.13
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's
>> ok
>> > [ ] -1 Do not release Apache Groovy 4.0.13 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>> >
>> > <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>Virus-free.www.avast.com <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> >
>> > <#m_-8806616514831804336_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> >
>>
>
>
> --
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud 
>
>- Blog: glaforge.dev
>- Twitter: @glaforge 
>- Mastodon: @glafo...@uwyn.net 
>
>

Re: [VOTE] Release Apache Groovy 3.0.18

[Andres Almiray]

+1 (binding)



On Mon, Jun 26, 2023 at 10:28 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Mon, Jun 26, 2023 at 10:14 AM Jochen Theodorou 
> wrote:
>
>> +1
>>
>> Am 26.06.23 um 08:53 schrieb Søren Berg Glasius:
>> > +1 (not binding)
>> >
>> > Med venlig hilsen,
>> > Søren Berg Glasius
>> >
>> > Hedevej 1, Gl. Rye, 8680 Ry
>> > Mobile: +45 40 44 91 88
>> > --- Press ESC once to quit - twice to save the changes.
>> >
>> >
>> > Den man. 26. jun. 2023 kl. 08.51 skrev Paul King > > >:
>> >
>> >
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 3.0.18 release!
>> >
>> > This release includes 34 bug fixes/improvements as outlined in the
>> > changelog:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353078
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353078
>> >
>> >
>> > Tag:
>> >
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_18
>> <
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_18
>> >
>> > Tag commit id: 07d4af6e4d3e5fbed2cf67ae0058bdcf83042e7f
>> >
>> > The artifacts to be voted on are located as follows (r62642).
>> > Source release:
>> > https://dist.apache.org/repos/dist/dev/groovy/3.0.18/sources
>> > 
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/3.0.18/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.18.
>> >
>> > 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.18
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's
>> ok
>> > [ ] -1 Do not release Apache Groovy 3.0.18 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>> >
>> > <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>Virus-free.www.avast.com <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> >
>> > <#m_4916143649572235556_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> >
>>
>
>
> --
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud 
>
>- Blog: glaforge.dev
>- Twitter: @glaforge 
>- Mastodon: @glafo...@uwyn.net 
>
>

Re: [EXT] [VOTE] Release Apache Groovy 4.0.12 (Take 2)

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 5 May 2023, at 21:36, Milles, Eric (TR Technology) via dev 
>  wrote:
> 
> 
> +1 (binding)
>  

Re: [VOTE] Release Apache Groovy 4.0.12

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 4 May 2023, at 9:04, Guillaume Laforge  wrote:+1 (binding)On Thu, May 4, 2023 at 1:20 AM Paul King  wrote:Dear development community,I am happy to start the VOTE thread for a Groovy 4.0.12 release!This release includes 30 bug fixes/improvements as outlined in the changelog:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353079Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_12Tag commit id: 8a591ebbc7634e2b52850a9d32a855318ad723d5The artifacts to be voted on are located as follows (r61627).Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.12/sourcesConvenience binaries: https://dist.apache.org/repos/dist/dev/groovy/4.0.12/distributionRelease artifacts are signed with a key from the following file:https://dist.apache.org/repos/dist/release/groovy/KEYSPlease vote on releasing this package as Apache Groovy 4.0.12.Reminder on ASF release approval requirements for PMC members:http://www.apache.org/legal/release-policy.html#release-approvalHints on validating checksums/signatures (but replace md5sum with sha256sum):https://www.apache.org/info/verification.htmlThe 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 4.0.12[ ]  0 I don't have a strong opinion about this, but I assume it's ok[ ] -1 Do not release Apache Groovy 4.0.12 because...Here is my vote:+1 (binding)
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 4.0.11

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 28 Mar 2023, at 7:48, Guillaume Laforge  wrote:+1 (binding)On Tue, Mar 28, 2023 at 3:52 AM Paul King  wrote:Dear development community,I am happy to start the VOTE thread for a Groovy 4.0.11 release!This release includes 11 bug fixes/improvements as outlined in the changelog:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353000Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_11Tag commit id: 698c68e35c8825d96360075b4e5f6f92ca0e0338The artifacts to be voted on are located as follows (r60861).Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.11/sourcesConvenience binaries: https://dist.apache.org/repos/dist/dev/groovy/4.0.11/distributionRelease artifacts are signed with a key from the following file:https://dist.apache.org/repos/dist/release/groovy/KEYSPlease vote on releasing this package as Apache Groovy 4.0.11.Reminder on ASF release approval requirements for PMC members:http://www.apache.org/legal/release-policy.html#release-approvalHints on validating checksums/signatures (but replace md5sum with sha256sum):https://www.apache.org/info/verification.htmlThe 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 4.0.11[ ]  0 I don't have a strong opinion about this, but I assume it's ok[ ] -1 Do not release Apache Groovy 4.0.11 because...Here is my vote:+1 (binding)Virus-free.www.avast.com
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 2.5.22

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 28 Mar 2023, at 7:48, Guillaume Laforge  wrote:+1 (binding)On Tue, Mar 28, 2023 at 1:38 AM Paul King  wrote:Dear development community,I am happy to start the VOTE thread for a Groovy 2.5.22 release!This release includes 23 bug fixes/improvements as outlined in the changelog:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352774Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_22Tag commit id: 60c4ff9ab31c62308180ac4702d5623be1d63cdcThe artifacts to be voted on are located as follows (r60858).Source release: https://dist.apache.org/repos/dist/dev/groovy/2.5.22/sourcesConvenience binaries: https://dist.apache.org/repos/dist/dev/groovy/2.5.22/distributionRelease artifacts are signed with a key from the following file:https://dist.apache.org/repos/dist/release/groovy/KEYSPlease vote on releasing this package as Apache Groovy 2.5.22.Reminder on ASF release approval requirements for PMC members:http://www.apache.org/legal/release-policy.html#release-approvalHints on validating checksums/signatures (but replace md5sum with sha256sum):https://www.apache.org/info/verification.htmlThe 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.22[ ]  0 I don't have a strong opinion about this, but I assume it's ok[ ] -1 Do not release Apache Groovy 2.5.22 because...Here is my vote:+1 (binding)Virus-free.www.avast.com
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 3.0.17

[Andres Almiray]

+1 (binding)Sent from my primitive tricorderOn 28 Mar 2023, at 7:48, Guillaume Laforge  wrote:+1 (binding)On Tue, Mar 28, 2023 at 2:00 AM Paul King  wrote:Dear development community,I am happy to start the VOTE thread for a Groovy 3.0.17 release!This release includes 5 bug fixes/improvements as outlined in the changelog:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352999Tag: https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_17Tag commit id: 72cac8ebdffce7d2c0d3486dbc658da32ec161baThe artifacts to be voted on are located as follows (r60859).Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.17/sourcesConvenience binaries: https://dist.apache.org/repos/dist/dev/groovy/3.0.17/distributionRelease artifacts are signed with a key from the following file:https://dist.apache.org/repos/dist/release/groovy/KEYSPlease vote on releasing this package as Apache Groovy 3.0.17.Reminder on ASF release approval requirements for PMC members:http://www.apache.org/legal/release-policy.html#release-approvalHints on validating checksums/signatures (but replace md5sum with sha256sum):https://www.apache.org/info/verification.htmlThe 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.17[ ]  0 I don't have a strong opinion about this, but I assume it's ok[ ] -1 Do not release Apache Groovy 3.0.17 because...Here is my vote:+1 (binding)Virus-free.www.avast.com
-- Guillaume LaforgeApache Groovy committerDeveloper Advocate @ Google CloudBlog: glaforge.devTwitter: @glaforgeMastodon: @glafo...@uwyn.net

Re: [VOTE] Release Apache Groovy 4.0.10

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Mar 9, 2023 at 9:56 AM Guillaume Laforge  wrote:

> +1 (binding)
>
> On Thu, Mar 9, 2023 at 8:21 AM Paul King  wrote:
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 4.0.10 release!
>>
>> This release includes 18 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352914
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_10
>> Tag commit id: 3efb64459746bf60941c5fdbb6413a711e64d543
>>
>> The artifacts to be voted on are located as follows (r60499).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.10/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.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 4.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 4.0.10
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.10 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>>
>>
>> 
>> Virus-free.www.avast.com
>> 
>> <#m_-7192379309042811694_m_7778821280445638438_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 3.0.16

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Mar 9, 2023 at 7:58 AM Guillaume Laforge  wrote:

> +1 (binding)
>
> Le jeu. 9 mars 2023, 06:41, Paul King  a écrit :
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 3.0.16 release!
>>
>> This release includes 15 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352913
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_16
>> Tag commit id: b25a7fe7e5dc970df534c1f6fc3c4de0ff9966f0
>>
>> The artifacts to be voted on are located as follows (r60497).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.16/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.16/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.16.
>>
>> 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.16
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 3.0.16 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>>
>>
>> 
>> Virus-free.www.avast.com
>> 
>> <#m_-3061424676153007926_m_-332478190691329145_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>

Re: [EXT] [VOTE] Release Apache Groovy 3.0.15

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Feb 6, 2023 at 8:28 PM Milles, Eric (TR Technology) via dev <
dev@groovy.apache.org> wrote:

> +1 (binding)
>
>
>
> *From:* Paul King 
> *Sent:* Sunday, February 5, 2023 2:30 PM
> *To:* Groovy_Developers 
> *Subject:* [EXT] [VOTE] Release Apache Groovy 3.0.15
>
>
>
> *External Email:* Use caution with links and attachments.
>
>
>
>
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.15 release!
>
> This release includes 15 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352706
> 
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_15
> 
> Tag commit id: 878cddd1fd27dcc5d124e0a1952582ceed90c2ff
>
> The artifacts to be voted on are located as follows (r59910).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.15/sources
> 
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.15/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.15.
>
> 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.15
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.15 because...
>
> Here is my vote:
>
> +1 (binding)
>
>
>

Re: [VOTE] Release Apache Groovy 4.0.9

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Feb 6, 2023 at 6:53 PM Daniel Sun  wrote:

> +1 (binding)
>
> Cheers,
> Daniel Sun
>
> On 2023/02/05 23:09:11 Paul King wrote:
> > Dear development community,
> >
> > I am happy to start the VOTE thread for a Groovy 4.0.9 release!
> >
> > This release includes 8 bug fixes/improvements as outlined in the
> changelog:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352775
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_9
> > Tag commit id: 9b747dff8ececa2d5ef09e03367b07cf93907917
> >
> > The artifacts to be voted on are located as follows (r59911).
> > Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.9/sources
> > Convenience binaries:
> > https://dist.apache.org/repos/dist/dev/groovy/4.0.9/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 4.0.9.
> >
> > 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 4.0.9
> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 4.0.9 because...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
>

Re: Next release(s)

[Andres Almiray]

A couple of inline comments but thanks for the pointers. I went ahead without making changes for the current releases. :-)Right. It was too close time-wise to adjust the release process with JReleaser. Once the current release is out we can have another look. Later Groovy versions (4+) are reproducible and so shouldn't need this double handling but the release scripts currently cater for both.OK. Then any changes to artifact upload procedures have to account for reproducible (4+) and non reproducible (3 & 2) as I’ve seen just a couple of releases posted for the latter. Likely additional security fixes might be needed in the coming years. Do you know whether after the release operation succeeds whether further syncing/caching occurs before artifacts might actually show up?AFAICT once a staged repository is closed & released it usually takes about 10 mins for artifacts to become available from the canonical repository. Mirrors and search.maven.org take at least 2hrs to be in sync. CheersAndresSent from my primitive tricorderOn 5 Feb 2023, at 23:53, Paul King  wrote:A couple of inline comments but thanks for the pointers. I went ahead without making changes for the current releases. :-)On Sat, Feb 4, 2023 at 1:31 AM Andres Almiray <aalmi...@gmail.com> wrote:Thanks Paul,I guess I'll have to create a map of tasks, their dependencies, and their behavior to have a better understanding of the release process.I can see that files are uploaded to an Artifactory instance - https://jreleaser.org/guide/latest/reference/upload/artifactory.html for Zips - https://jreleaser.org/guide/latest/reference/deploy/maven/artifactory.html for JARs, POMsFiles are downloaded from Artifactory to later be synced to Maven Central  - https://jreleaser.org/guide/latest/reference/download/http.html download files - https://jreleaser.org/guide/latest/reference/deploy/maven/nexus2.html deploy to MC. Status for close and release operations are polled automaticallyDo you know whether after the release operation succeeds whether further syncing/caching occurs before artifacts might actually show up? Release notes are populated with information provided by Jira. JReleaser doesn't offer this kind of integration yet, but it could do so in the future.Cheers,Andres---Java Champion; Groovy Enthusiasthttps://andresalmiray.comhttps://www.linkedin.com/in/aalmiray--What goes up, must come down. Ask any system administrator.There are 10 types of people in the world: Those who understand binary, and those who don't.To understand recursion, we must first understand recursion.On Thu, Feb 2, 2023 at 12:57 AM Paul King <pa...@asert.com.au> wrote:As long as we use the release manager's Apache email address, the current announcer sounds like it will be fine.We currently wait until artifacts have synced with Maven Central before sending the email.Currently that's a manual step. See adhoc.gradle#checkMavenStatus. It wouldn't be hard to tweak that though.On Thu, Feb 2, 2023 at 2:30 AM Andres Almiray <aalmi...@gmail.com> wrote:Hi Paul,Great. Thank you for that explanation. Saved me a lot of time searching :DAt the moment the SMTP announcer can only configure a single sender, single message, multiple recipients.I could imagine the following scenarios:1. multiple senders, same message2. single sender, multiple messages3. multiple senders, each one with different or shared messageDo any of these make sense for Groovy given its current release settings? If so I'd have to add code to JReleaser to support them.Cheers,Andres---Java Champion; Groovy Enthusiasthttps://andresalmiray.comhttps://www.linkedin.com/in/aalmiray--What goes up, must come down. Ask any system administrator.There are 10 types of people in the world: Those who understand binary, and those who don't.To understand recursion, we must first understand recursion.On Wed, Feb 1, 2023 at 2:26 PM Paul King <pa...@asert.com.au> wrote:Hi Andres,It's been on my TODO list to incorporate JReleaser where we can but I haven't found the cycles to date.Your suggestion is certainly a possibility!The release process (two phases to allow for ASF voting) is driven by the Gradle scripts in:https://github.com/apache/groovy-release/These in turn call into the normal build from https://github.com/apache/groovy as needed.So, a PR (or two) could be against either (or both) of these repos.In some ways it would be nice to drive everything from within the groovy repo itselfbut that isn't a thing for the next release!In terms of what happens now, phase2.gradle in the groovy-release repo has theannounceReleaseOnSDKman task which ultimately triggers the current tweet from sdkman.The email is crafted by the proposeAnnouncementEmail task but currently cut-n-pastedby the release manager and sometimes adjusted by hand. It is sent to the Groovy dev, usersand ASF-wide announce mailing lists.At the moment, we don't have t

Re: Next release(s)

[Andres Almiray]

Thanks Paul,

I guess I'll have to create a map of tasks, their dependencies, and their
behavior to have a better understanding of the release process.

I can see that files are uploaded to an Artifactory instance
 - https://jreleaser.org/guide/latest/reference/upload/artifactory.html for
Zips
 -
https://jreleaser.org/guide/latest/reference/deploy/maven/artifactory.html
for JARs, POMs

Files are downloaded from Artifactory to later be synced to Maven Central
 - https://jreleaser.org/guide/latest/reference/download/http.html download
files
 - https://jreleaser.org/guide/latest/reference/deploy/maven/nexus2.html
deploy to MC. Status for close and release operations are polled
automatically

Release notes are populated with information provided by Jira. JReleaser
doesn't offer this kind of integration yet, but it could do so in the
future.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Feb 2, 2023 at 12:57 AM Paul King  wrote:

> As long as we use the release manager's Apache email address, the current
> announcer sounds like it will be fine.
> We currently wait until artifacts have synced with Maven Central before
> sending the email.
> Currently that's a manual step. See adhoc.gradle#checkMavenStatus. It
> wouldn't be hard to tweak that though.
>
> On Thu, Feb 2, 2023 at 2:30 AM Andres Almiray  wrote:
>
>> Hi Paul,
>>
>> Great. Thank you for that explanation. Saved me a lot of time searching :D
>>
>> At the moment the SMTP announcer can only configure a single sender,
>> single message, multiple recipients.
>> I could imagine the following scenarios:
>>
>> 1. multiple senders, same message
>> 2. single sender, multiple messages
>> 3. multiple senders, each one with different or shared message
>>
>> Do any of these make sense for Groovy given its current release settings?
>> If so I'd have to add code to JReleaser to support them.
>>
>> Cheers,
>> Andres
>>
>> ---
>> Java Champion; Groovy Enthusiast
>> https://andresalmiray.com
>> https://www.linkedin.com/in/aalmiray
>> --
>> What goes up, must come down. Ask any system administrator.
>> There are 10 types of people in the world: Those who understand binary,
>> and those who don't.
>> To understand recursion, we must first understand recursion.
>>
>>
>> On Wed, Feb 1, 2023 at 2:26 PM Paul King  wrote:
>>
>>> Hi Andres,
>>>
>>> It's been on my TODO list to incorporate JReleaser where we can but I
>>> haven't found the cycles to date.
>>> Your suggestion is certainly a possibility!
>>>
>>> The release process (two phases to allow for ASF voting) is driven by
>>> the Gradle scripts in:
>>>
>>> https://github.com/apache/groovy-release/
>>>
>>> These in turn call into the normal build from
>>> https://github.com/apache/groovy as needed.
>>>
>>> So, a PR (or two) could be against either (or both) of these repos.
>>> In some ways it would be nice to drive everything from within the groovy
>>> repo itself
>>> but that isn't a thing for the next release!
>>>
>>> In terms of what happens now, phase2.gradle in the groovy-release repo
>>> has the
>>> announceReleaseOnSDKman task which ultimately triggers the current tweet
>>> from sdkman.
>>> The email is crafted by the proposeAnnouncementEmail task but currently
>>> cut-n-pasted
>>> by the release manager and sometimes adjusted by hand. It is sent to the
>>> Groovy dev, users
>>> and ASF-wide announce mailing lists.
>>>
>>> At the moment, we don't have the credentials for @ApacheGroovy (on
>>> twitter) or
>>> @apachegro...@fosstodon.org as info necessarily needed by release
>>> managers
>>> (though possibly we should).
>>>
>>> Also, in order for the email to the ASF announce mailing list to pass
>>> through moderation,
>>> it needs to be sent from an Apache email address. This isn't part of the
>>> current automation.
>>>
>>> I'm happy to help where I can.
>>>
>>> Cheers, Paul.
>>>
>>>
>>> On Wed, Feb 1, 2023 at 10:48 PM Andres Almiray 
>>> wrote:
>>>
>>>> Hi Paul,
>>>>
>>>> T

Re: Next release(s)

[Andres Almiray]

Hi Paul,

Great. Thank you for that explanation. Saved me a lot of time searching :D

At the moment the SMTP announcer can only configure a single sender, single
message, multiple recipients.
I could imagine the following scenarios:

1. multiple senders, same message
2. single sender, multiple messages
3. multiple senders, each one with different or shared message

Do any of these make sense for Groovy given its current release settings?
If so I'd have to add code to JReleaser to support them.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Feb 1, 2023 at 2:26 PM Paul King  wrote:

> Hi Andres,
>
> It's been on my TODO list to incorporate JReleaser where we can but I
> haven't found the cycles to date.
> Your suggestion is certainly a possibility!
>
> The release process (two phases to allow for ASF voting) is driven by the
> Gradle scripts in:
>
> https://github.com/apache/groovy-release/
>
> These in turn call into the normal build from
> https://github.com/apache/groovy as needed.
>
> So, a PR (or two) could be against either (or both) of these repos.
> In some ways it would be nice to drive everything from within the groovy
> repo itself
> but that isn't a thing for the next release!
>
> In terms of what happens now, phase2.gradle in the groovy-release repo has
> the
> announceReleaseOnSDKman task which ultimately triggers the current tweet
> from sdkman.
> The email is crafted by the proposeAnnouncementEmail task but currently
> cut-n-pasted
> by the release manager and sometimes adjusted by hand. It is sent to the
> Groovy dev, users
> and ASF-wide announce mailing lists.
>
> At the moment, we don't have the credentials for @ApacheGroovy (on
> twitter) or
> @apachegro...@fosstodon.org as info necessarily needed by release managers
> (though possibly we should).
>
> Also, in order for the email to the ASF announce mailing list to pass
> through moderation,
> it needs to be sent from an Apache email address. This isn't part of the
> current automation.
>
> I'm happy to help where I can.
>
> Cheers, Paul.
>
>
> On Wed, Feb 1, 2023 at 10:48 PM Andres Almiray  wrote:
>
>> Hi Paul,
>>
>> Though not strictly related to new features, what are your thoughts on
>> configuring JReleaser for posting announcements to all supported
>> distribution channels?
>> The tool can post to Twitter, Mastodon, and send an e-mail via its SMTP
>> announcers.
>>
>> If it makes sense, I can craft a PR which could be tested before the next
>> release.
>> Or given any time constraints we may test it after the next release :D
>>
>> Cheers,
>> Andres
>>
>> ---
>> Java Champion; Groovy Enthusiast
>> https://andresalmiray.com
>> https://www.linkedin.com/in/aalmiray
>> --
>> What goes up, must come down. Ask any system administrator.
>> There are 10 types of people in the world: Those who understand binary,
>> and those who don't.
>> To understand recursion, we must first understand recursion.
>>
>>
>> On Wed, Feb 1, 2023 at 1:43 PM Paul King  wrote:
>>
>>>
>>> Hi folks, I might try to do a 4.0.9 late this week or early next week.
>>> This is mostly to incorporate some OSGi fixes. It turns out all Groovy 4
>>> releases until now have a minor glitch for certain OSGi environments.
>>>
>>> I might also do a bump on 3_0_X if I have time.
>>>
>>> It's time to get in any desired fixes or let me know if there are
>>> reasons to push this back a little more.
>>>
>>> Cheers, Paul.
>>>
>>>

Re: Next release(s)

[Andres Almiray]

Hi Paul,

Though not strictly related to new features, what are your thoughts on
configuring JReleaser for posting announcements to all supported
distribution channels?
The tool can post to Twitter, Mastodon, and send an e-mail via its SMTP
announcers.

If it makes sense, I can craft a PR which could be tested before the next
release.
Or given any time constraints we may test it after the next release :D

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Feb 1, 2023 at 1:43 PM Paul King  wrote:

>
> Hi folks, I might try to do a 4.0.9 late this week or early next week.
> This is mostly to incorporate some OSGi fixes. It turns out all Groovy 4
> releases until now have a minor glitch for certain OSGi environments.
>
> I might also do a bump on 3_0_X if I have time.
>
> It's time to get in any desired fixes or let me know if there are reasons
> to push this back a little more.
>
> Cheers, Paul.
>
>

Re: [VOTE] Release Apache Groovy 4.0.8

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Jan 19, 2023 at 8:59 AM Guillaume Laforge 
wrote:

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

Re: [VOTE] Release Apache Groovy 2.5.21

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Jan 19, 2023 at 8:59 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Thu, Jan 19, 2023 at 5:53 AM Paul King  wrote:
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 2.5.21 release!
>>
>> This release includes 11 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352705
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_21
>> Tag commit id: 9c3bd94dee0e6c7804a3054045dee233e20faa54
>>
>> The artifacts to be voted on are located as follows (r59437).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/2.5.21/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/2.5.21/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 2.5.21.
>>
>> 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.21
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.5.21 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 2.5.20

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Dec 21, 2022 at 3:48 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Wed, Dec 21, 2022 at 8:09 AM Daniel Sun  wrote:
>
>> +1 (binding)
>>
>> Cheers,
>> Daniel Sun
>>
>> On 2022/12/21 03:43:38 Paul King wrote:
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 2.5.20 release!
>> >
>> > This release includes 9 bug fixes/improvements as outlined in the
>> changelog:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352406
>> >
>> > Tag:
>> >
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_20
>> > Tag commit id: 2774ea7e5b0eb4cf904153d78a0f91479b17ef54
>> >
>> > The artifacts to be voted on are located as follows (r58828).
>> > Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/2.5.20/sources
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/2.5.20/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 2.5.20.
>> >
>> > 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.20
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> > [ ] -1 Do not release Apache Groovy 2.5.20 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 4.0.7

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Dec 21, 2022 at 3:48 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Wed, Dec 21, 2022 at 8:08 AM Daniel Sun  wrote:
>
>> groovySh and groovyConsole work well.
>>
>> +1 (binding)
>>
>> Cheers,
>> Daniel Sun
>>
>> On 2022/12/21 06:00:15 Paul King wrote:
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 4.0.7 release!
>> >
>> > This release includes 68 bug fixes/improvements as outlined in the
>> > changelog:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352407
>> >
>> > Tag:
>> >
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_7
>> > Tag commit id: b82d3bfc4758b8634e4e8482aab52d8dea6bafd4
>> >
>> > The artifacts to be voted on are located as follows (r58830).
>> > Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.7/sources
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/4.0.7/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 4.0.7.
>> >
>> > 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 4.0.7
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> > [ ] -1 Do not release Apache Groovy 4.0.7 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 3.0.14

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Dec 21, 2022 at 3:48 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Wed, Dec 21, 2022 at 8:09 AM Daniel Sun  wrote:
>
>> +1 (binding)
>>
>> Cheers,
>> Daniel Sun
>>
>> On 2022/12/21 05:04:05 Paul King wrote:
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 3.0.14 release!
>> >
>> > This release includes 26 bug fixes/improvements as outlined in the
>> > changelog:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352311
>> >
>> > Tag:
>> >
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_14
>> > Tag commit id: f5c9a7120441f55669aba44c2e58d3d6fb693481
>> >
>> > The artifacts to be voted on are located as follows (r58829).
>> > Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.14/sources
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/3.0.14/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.14.
>> >
>> > 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.14
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> > [ ] -1 Do not release Apache Groovy 3.0.14 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 4.0.6

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 13 Oct 2022, at 8:41, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 4.0.6 release!
> 
> This release includes 14 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352278
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_6
> Tag commit id: 16b32e9a79003533c42ca542da8b051cc398aad4
> 
> The artifacts to be voted on are located as follows (r57347).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.6/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.6/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 4.0.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 4.0.6
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.6 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: [EXT] [VOTE] Release Apache Groovy 2.5.19

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 13 Oct 2022, at 19:18, Milles, Eric (TR Technology) via dev 
>  wrote:
> 
> +1 (binding)
> 
> -Original Message-
> From: Paul King  
> Sent: Wednesday, October 12, 2022 10:59 PM
> To: Groovy_Developers 
> Subject: [EXT] [VOTE] Release Apache Groovy 2.5.19
> 
> External Email: Use caution with links and attachments.
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 2.5.19 release!
> 
> This release includes 72 bug fixes/improvements as outlined in the changelog:
> https://urldefense.com/v3/__https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352130__;!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG7MXPCUNw$
>   
> 
> Tag: 
> https://urldefense.com/v3/__https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs*tags*GROOVY_2_5_19__;Ly8!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG5IcTl0dw$
> Tag commit id: 56ee657bc629d1957361903ffa4051a48efa0575
> 
> The artifacts to be voted on are located as follows (r57340).
> Source release: 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/groovy/2.5.19/sources__;!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG7ecY-s2w$
> Convenience binaries:
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/groovy/2.5.19/distribution__;!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG68-7sm_A$
>   
> 
> Release artifacts are signed with a key from the following file:
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/groovy/KEYS__;!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG5Xc5n9sA$
>   
> 
> Please vote on releasing this package as Apache Groovy 2.5.19.
> 
> Reminder on ASF release approval requirements for PMC members:
> https://urldefense.com/v3/__http://www.apache.org/legal/release-policy.html*release-approval__;Iw!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG7X2fhk6A$
> Hints on validating checksums/signatures (but replace md5sum with sha256sum):
> https://urldefense.com/v3/__https://www.apache.org/info/verification.html__;!!GFN0sa3rsbfR8OLyAw!YV-CSN5XWBphI2UMZGfLrZICeEdTFfZl4ueLraIlvCae3SJp6B2BgWzP-QCl2XVEPJhbtKCTPvBlgG4wrgYyQQ$
>   
> 
> 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.19
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok [ ] -1 
> Do not release Apache Groovy 2.5.19 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: [VOTE] Release Apache Groovy 3.0.13

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Sep 15, 2022 at 8:46 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.13 release!
>
> This release includes 44 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352131
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_13
> Tag commit id: d79d8a71ae32f3c4547058bd63b88fff80f86c67
>
> The artifacts to be voted on are located as follows (r56823).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.13/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.13/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.13.
>
> 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.13
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.13 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 4.0.5

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Sep 6, 2022 at 3:23 PM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.5 release!
>
> This release includes 56 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352126
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_5
> Tag commit id: 62a1836e81efaeec21f7b49e18dcb3f97f0c056f
>
> The artifacts to be voted on are located as follows (r56688).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.5/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.5/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 4.0.5.
>
> 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 4.0.5
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.5 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: Removing some old pre-release doco

[Andres Almiray]

+1

I think this is the sensible thing to do. 

Sent from my primitive tricorder

> On 24 Jul 2022, at 13:45, Paul King  wrote:
> 
> Hi folks,
> 
> I was thinking of removing some old versions of the doco. It isn't
> that disk space is particularly tight but I think it is just easier
> for folks to find versions they are after with less clutter from the
> noisy pre-release versions. I was thinking of getting rid of:
> 
> '2.5.0-rc-1', '2.5.0-rc-2', '2.5.0-rc-3' (we'd be left with 2.5.0
> through 2.5.18)
> 
> '3.0.0-alpha-1', '3.0.0-alpha-2', '3.0.0-alpha-3', '3.0.0-alpha-4',
> '3.0.0-beta-1', '3.0.0-beta-2', '3.0.0-beta-3' (we'd be left with the
> RCs and 3.0.0 thru 3.0.12)
> 
> '4.0.0-alpha-1', '4.0.0-alpha-2', '4.0.0-alpha-3' (we'd be left with
> the betas, RCs and 4.0.0 - 4.0.4)
> 
> This wouldn't impact any actual releases (including doc zips) which
> would all remain, just the online versions of the docs for those
> pre-release versions. Changelogs or versions in Jira would also not be
> touched.
> 
> Any objections?
> 
> Thanks, Paul.

Re: [VOTE] Release Apache Groovy 4.0.4

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 20 Jul 2022, at 8:40, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 4.0.4 release!
> 
> This release includes 42 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351811
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_4
> Tag commit id: 4d7762e98b2e881bfc7ea320a6901fabc264
> 
> The artifacts to be voted on are located as follows (r55862).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.4/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.4/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 4.0.4.
> 
> 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 4.0.4
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.4 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: [VOTE] Release Apache Groovy 3.0.12

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 20 Jul 2022, at 4:08, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.12 release!
> 
> This release includes 21 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351799
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_12
> Tag commit id: 486d57f832a577ad2c574868e3540ebe21c44abb
> 
> The artifacts to be voted on are located as follows (r55859).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.12/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.12/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.12.
> 
> 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.12
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.12 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: [VOTE] Release Apache Groovy 2.5.18

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 20 Jul 2022, at 3:32, Paul King  wrote:
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 2.5.18 release!
> 
> This release includes 14 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351798
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_18
> Tag commit id: 0e9636a03d7b2748ace1dcde87fa3680ae74fc9e
> 
> The artifacts to be voted on are located as follows (r55858).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/2.5.18/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.18/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 2.5.18.
> 
> 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.18
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.18 because...
> 
> Here is my vote:
> 
> +1 (binding)

Re: Welcome Remko Popma to the Apache Groovy PMC!

[Andres Almiray]

Welcome! Great to have you in the team 

Sent from my primitive tricorder

> On 13 Jul 2022, at 9:59, Paul King  wrote:
> 
> Remko Popma has been voted as an additional member to the Apache
> Groovy PMC. Congratulations Remko!
> 
> Remko has been a committer for some time, and was the main contributor
> for the groovy-cli-picocli module. He is also on the PMC of Apache
> Logging.
> 
> Cheers, Paul.
> On behalf of the Apache Groovy PMC.

Re: [VOTE] Release Apache Groovy 4.0.3 (take 2)

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 2 Jun 2022, at 0:30, Remko Popma  wrote:
> 
> 
> +1
> 
>> On Wed, Jun 1, 2022 at 9:04 PM Jochen Theodorou  wrote:
>> +1 (binding)
>> 
>> On 01.06.22 13:24, Guillaume Laforge wrote:
>> > +1 (binding)
>> >
>> > On Wed, Jun 1, 2022 at 12:49 PM Paul King > > > wrote:
>> >
>> > [This fixes the groovysh issue Daniel found.]
>> >
>> > Dear development community,
>> >
>> > I am happy to start the VOTE thread for a Groovy 4.0.3 release!
>> >
>> > This release includes 40 bug fixes/improvements as outlined in the
>> > changelog:
>> > 
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351650
>> > 
>> > 
>> >
>> > Tag:
>> > 
>> > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_3
>> > 
>> > 
>> > Tag commit id: 63283624d3b87d5bcb6688bc238c126d829dbc6d
>> >
>> > The artifacts to be voted on are located as follows (r54813).
>> > Source release:
>> > https://dist.apache.org/repos/dist/dev/groovy/4.0.3/sources
>> > 
>> > Convenience binaries:
>> > https://dist.apache.org/repos/dist/dev/groovy/4.0.3/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 4.0.3.
>> >
>> > 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 4.0.3
>> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> > [ ] -1 Do not release Apache Groovy 4.0.3 because...
>> >
>> > Here is my vote:
>> >
>> > +1 (binding)
>> >
>> >
>> >
>> > --
>> > Guillaume Laforge
>> > Apache Groovy committer
>> > Developer Advocate @ Google Cloud Platform
>> >
>> > Blog: http://glaforge.appspot.com/ 
>> > Twitter: @glaforge 
>> 

Re: [VOTE] Release Apache Groovy 3.0.11

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, May 29, 2022 at 4:50 AM Paul King  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=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)
>

Re: [VOTE] Release Apache Groovy 2.5.17

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, May 29, 2022 at 4:19 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.17 release!
>
> This release includes 23 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351416
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_17
> Tag commit id: 406ac1fb39cc9d24b2ffbce9e86386b1993b3c84
>
> The artifacts to be voted on are located as follows (r54773).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.17/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.17/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 2.5.17.
>
> 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.17
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.17 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 4.0.3

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, May 29, 2022 at 6:25 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.3 release!
>
> This release includes 40 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351650
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_3
> Tag commit id: 7d1634595502170593da9cca3120c158867dfecf
>
> The artifacts to be voted on are located as follows (r54775).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.3/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.3/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 4.0.3.
>
> 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 4.0.3
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.3 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 4.0.2

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 19 Apr 2022, at 10:36, Guillaume Laforge  wrote:
> 
> 
> +1 (binding)
> 
> Built from source, all tests green!
> Some manual tests in the console, fine too.
> 
> Guillaume
>  
> 
>> On Tue, Apr 19, 2022 at 3:00 PM Paul King  wrote:
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 4.0.2 release!
>> 
>> This release includes 47 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351424
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_2
>> Tag commit id: a3bb54f30c83574031e0954fd964a68cb31a3312
>> 
>> The artifacts to be voted on are located as follows (r53962).
>> Source release: https://dist.apache.org/repos/dist/dev/groovy/4.0.2/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.2/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 4.0.2.
>> 
>> 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 4.0.2
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.2 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
> 
> 
> -- 
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
> 
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge

Re: [VOTE] Release Apache Groovy 4.0.1 (take 3)

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sat, Mar 5, 2022 at 12:29 PM Paul King  wrote:

>
> I checked all files under META_INF/services this time. All looks okay.
>
> ==
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.1 release!
>
> This release includes 40 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351284
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_1
> Tag commit id: 40530f2812e37af8dc13d8d3fbc8ccef7497378f
>
> The artifacts to be voted on are located as follows (r52876).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/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 4.0.1.
>
> 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 4.0.1
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.1 because...
>
> Here is my vote:
>
> +1 (binding)
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-478666555262675_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 3.0.10 (take 2 after jarjar fix)

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Mar 3, 2022 at 11:36 AM Guillaume Laforge 
wrote:

> +1 (binding)
>
> On Thu, Mar 3, 2022 at 11:19 AM Paul King  wrote:
>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 3.0.10 release!
>>
>> This release includes 91 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350584
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_10
>> Tag commit id: 32772a0f79de58849cf0eea0b8d728d4b3d80ef2
>>
>> The artifacts to be voted on are located as follows (r52829).
>> 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 
>

Re: [VOTE] Release Apache Groovy 4.0.1 (take 2)

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Mar 3, 2022 at 3:53 PM Guillaume Laforge  wrote:

> +1 (binding)
>
> On Thu, Mar 3, 2022 at 3:18 PM Paul King  wrote:
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 4.0.1 release!
>>
>> This release includes 40 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351284
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_1
>> Tag commit id: 0e0ffcfd84a32094e7ea6422699c4b0568c7d8a7
>>
>> The artifacts to be voted on are located as follows (r52835).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/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 4.0.1.
>>
>> 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 4.0.1
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.1 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_-4609821475840056183_m_2865129203309962704_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 2.5.16 (real version)

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Mar 2, 2022 at 5:41 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.16 release!
>
> This release includes 108 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350583
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_16
> Tag commit id: bcf72d3fe865c971682bdcf1f0679623328afd13
>
> The artifacts to be voted on are located as follows (r52804).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.16/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.16/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 2.5.16.
>
> 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.16
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.16 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 4.0.1

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Mar 2, 2022 at 6:33 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.1 release!
>
> This release includes 40 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351284
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_1
> Tag commit id: 46976eec3670418873d69c0577ceda00b38fd754
>
> The artifacts to be voted on are located as follows (r52805).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.1/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 4.0.1.
>
> 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 4.0.1
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.1 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 3.0.10

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Mar 2, 2022 at 5:41 AM Paul King  wrote:

> 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=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)
>

Re: [VOTE] Release Apache Groovy 4.0.0

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Jan 25, 2022 at 12:49 PM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.0 release!
>
> This release includes 28 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351156
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0
> Tag commit id: 44db8b9dc41c28b9d5acb0df2d2acefc2990e021
>
> The artifacts to be voted on are located as follows (r52262).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0/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 4.0.0.
>
> 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 4.0.0
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.0 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 4.0.0-rc-2

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 24 Dec 2021, at 9:33, Guillaume Laforge  wrote:
> 
> 
> +1 (binding)
> 
> Le ven. 24 déc. 2021, 00:50, Paul King  a écrit :
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 4.0.0-rc-2 release!
>> 
>> This release includes 52 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350895
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_RC_2
>> Tag commit id: d2f45668bd5dd9cc33be816e869ddbcebb815a54
>> 
>> The artifacts to be voted on are located as follows (r51748).
>> Source release: 
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-2/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-2/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 4.0.0-rc-2.
>> 
>> 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 4.0.0-rc-2
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.0-rc-2 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)

Re: [VOTE] Release Apache Groovy 4.0.0-rc-1

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Nov 2021, at 12:05, Remko Popma  wrote:
> 
> 
> +1
> Remko
> 
>> On Sat, Nov 27, 2021 at 10:13 AM Paul King  wrote:
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 4.0.0-rc-1 release!
>> 
>> This release includes 26 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350848
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_RC_1
>> Tag commit id: 2555ed859b37af21fad2621c83f89db59cbd9030
>> 
>> The artifacts to be voted on are located as follows (r51109).
>> Source release: 
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-1/sources
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-1/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 4.0.0-rc-1.
>> 
>> 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 4.0.0-rc-1
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.0-rc-1 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)

Re: [VOTE] Release Apache Groovy 4.0.0-beta-2

[Andres Almiray]

+1 (binding)
---
Java Champion; Groovy Enthusiast
https://andresalmiray.com
https://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sat, Nov 6, 2021 at 1:30 AM Paul King  wrote:

> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.0-beta-2 release!
>
> This release includes 104 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350212
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_BETA_2
> Tag commit id: 666b0084241f10293aa57175664ab4ca9764e3cb
>
> The artifacts to be voted on are located as follows (r50820).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-beta-2/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-beta-2/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 4.0.0-beta-2.
>
> 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 4.0.0-beta-2
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.0-beta-2 because...
>
> Here is my vote:
>
> +1 (binding)
>

Re: [VOTE] Release Apache Groovy 2.5.15

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 3 Sep 2021, at 10:48, Guillaume Laforge  wrote:
> 
> 
> +1 (binding)
> 
> Gradle build scan:
> https://gradle.com/s/zueoks7vtlrsg
> 
> Guillaume
> 
> 
>> On Fri, Sep 3, 2021 at 8:15 AM Søren Berg Glasius  wrote:
>> +1
>> 
>> 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 fre. 3. sep. 2021 kl. 03.54 skrev Paul King :
>>> 
>>> Dear development community,
>>> 
>>> I am happy to start the VOTE thread for a Groovy 2.5.15 release!
>>> 
>>> This release includes 42 bug fixes/improvements as outlined in the 
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12349466
>>> 
>>> Tag: 
>>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_15
>>> Tag commit id: 4421ab5a0c64eccac7ac6100307bd966e2c09071
>>> 
>>> The artifacts to be voted on are located as follows (r49730).
>>> Source release: https://dist.apache.org/repos/dist/dev/groovy/2.5.15/sources
>>> Convenience binaries: 
>>> https://dist.apache.org/repos/dist/dev/groovy/2.5.15/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 2.5.15.
>>> 
>>> 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.15
>>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>>> [ ] -1 Do not release Apache Groovy 2.5.15 because...
>>> 
>>> Here is my vote:
>>> 
>>> +1 (binding)
>>> 
> 
> 
> -- 
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
> 
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge

Re: [VOTE] Release Apache Groovy 3.0.8

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 16 Apr 2021, at 22:13, Milles, Eric (TR Technology) 
>  wrote:
> 
> 
> +1
>  
> From: Paul King  
> Sent: Friday, April 16, 2021 3:59 AM
> To: Groovy_Developers 
> Subject: [VOTE] Release Apache Groovy 3.0.8
>  
>  
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.8 release!
> 
> This release includes 92 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12349467
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_8
> Tag commit id: d7684d101d64ca6da28fdb8069ea92475d011168
> 
> The artifacts to be voted on are located as follows (r-1).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.8/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/3.0.8/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 3.0.8.
> 
> 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.8
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.8 because...
> 
> Here is my vote:
> 
> +1 (binding)
>  

Re: [VOTE] Release Apache Groovy 4.0.0-alpha-3

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 14 Apr 2021, at 2:45, Milles, Eric (TR Technology) 
>  wrote:
> 
> 
> +1
>  
> From: Paul King  
> Sent: Monday, April 12, 2021 9:57 PM
> To: Groovy_Developers 
> Subject: [VOTE] Release Apache Groovy 4.0.0-alpha-3
>  
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 4.0.0-alpha-3 release!
> 
> This release includes 152 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12349469
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_ALPHA_3
> Tag commit id: bdd219508feef5893372bf1b96ead893f2f2869b
> 
> The artifacts to be voted on are located as follows (r47022).
> Source release: 
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-3/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-3/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 4.0.0-alpha-3.
> 
> 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 4.0.0-alpha-3
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.0-alpha-3 because...
> 
> Here is my vote:
> 
> +1 (binding)
>  

Re: ApacheCon 2021

[Andres Almiray]

Count me in as well! 

Sent from my primitive tricorder

> On 17 Feb 2021, at 13:30, Paul King  wrote:
> 
> 
> 
> Hi Folks,
> 
> Very early planning for ApacheCon 2021 has started. No details as yet. I have 
> tentatively put my hand up to be involved with putting together a Groovy 
> track like we did last year. I'd be keen for any feedback and let me know if 
> you are interested in helping out.
> 
> Cheers, Paul.
> 
> 
>   Virus-free. www.avast.com

Re: Proposal handling of potential variable declarations for expressions starting with an underscore or dollar

[Andres Almiray]

As I recall the use of a single _ as variable name is restricted since JDK10 
and will become an error in newer JDKs. 

Does the use of a leading _ in an identifier has been discouraged as well in 
newer JDKs? If so then we should do the same even of means breaking 
compatibility. 

Cheers
Andres

Sent from my primitive tricorder

> On 11 Feb 2021, at 10:58, Mario Garcia  wrote:
> 
> 
> If it helps, I've seen some programmers with python background using the 
> underscore in Groovy for method declaration. It seems they use the convention 
> of the underscore prefix to note these methods aren't for public consumption.
> 
>> El jue, 11 feb 2021 a las 9:49, Paul King () 
>> escribió:
>> 
>> Hi folks,
>> 
>> I would be interested in any thoughts about the following issue:
>> 
>> https://issues.apache.org/jira/browse/GROOVY-9936
>> 
>> TL;DR There is an edge case where Groovy 3 (Parrot) behavior now differs 
>> from the old parser. Even though an argument could be made either way as to 
>> which behavior is better, I propose we align with the old parser.
>> 
>> Proposed PR:
>> 
>> https://github.com/apache/groovy/pull/1485
>> 
>> Let me know your thoughts.
>> 
>> Thanks, Paul.
>> 
>> 
>>  Virus-free. www.avast.com

Re: [VOTE] Release Apache Groovy 4.0.0-alpha-2 (take 2)

[Andres Almiray]

+1 (Binding)


On Tue, Dec 1, 2020 at 4:11 PM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 4.0.0-alpha-2 release!
>
> NOTE: If building from source, please observe the slightly changed
> instructions for bootstrapping gradle in the README.adoc!
>
> This release includes 60 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348839
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_ALPHA_2
> Tag commit id: 1136910170fd100fb2d792db95ec08b935f29530
>
> The artifacts to be voted on are located as follows (r44782).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-2/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-2/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 4.0.0-alpha-2.
>
> 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 4.0.0-alpha-2
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 4.0.0-alpha-2 because...
>
> Here is my vote:
>
> +1 (binding)
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-6834864843580124984_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 3.0.7

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Nov 30, 2020 at 8:00 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.7 release!
>
> This release includes 52 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348838
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_7
> Tag commit id: a43f54cb59f19218a9cbc9edb3741dbd4a2e2e77
>
> The artifacts to be voted on are located as follows (r44743).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.7/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.7/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 3.0.7.
>
> 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.7
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.7 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 2.4.21

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Nov 30, 2020 at 6:36 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.4.21 release!
>
> This release includes 6 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348619
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_21
> Tag commit id: 41b990d0a20e442f29247f0e04cbed900f3dcad4
>
> The artifacts to be voted on are located as follows (r44741).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.4.21/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.4.21/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.4.21.
>
> 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.4.21
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.4.21 because...
>
> Here is my vote:
>
> +1 (binding)
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-8859585350083792318_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Re: [VOTE] Release Apache Groovy 4.0.0-alpha-1

[Andres Almiray]

FWIW it looks like the rendering of "Note" elements is a bit off

http://groovy-lang.org/releasenotes/groovy-4.0.html

The word "Note" is rendered with the same font size and weight as the
content.
there's no spacing between "Note" and the content.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Sep 28, 2020 at 11:31 AM Paul King  wrote:

> Thanks Cédric, I created this:
>
> https://issues.apache.org/jira/browse/GROOVY-9761
>
> Cheers, Paul.
> PRs welcome ;-)
>
>
> On Mon, Sep 28, 2020 at 6:52 PM Cédric Champeau 
> wrote:
>
>> Congrats on having the first alpha, team! I'm just re-instantiating that
>> because of the coordinates change, it would really be great if you could
>> leverage Gradle Module Metadata so that users are aware of a conflict, and
>> that Gradle can take care of it. This is basically about saying that
>> org.apache.groovy provides the same capabiliy as org.codehaus.groovy. Of
>> course requires you to update the build to use maven-publish, which you
>> have to do anyway before Gradle 7.0 is out
>>
>> Le lun. 28 sept. 2020 à 09:46, Paul King  a écrit :
>>
>>> Thanks for voting everyone. 24 hrs to go, though we have the required
>>> numbers if nothing changes.
>>>
>>> Here is a draft of the Groovy 4 release notes if anyone wants to check I
>>> haven't forgotten anything:
>>>
>>> http://groovy-lang.org/releasenotes/groovy-4.0.html
>>>
>>>
>>> Cheers, Paul.
>>>
>>>
>>> On Sat, Sep 26, 2020 at 11:19 PM Paul King  wrote:
>>>

 Dear development community,

 I am happy to start the VOTE thread for a Groovy 4.0.0-alpha-1 release!

 This release includes 252 bug fixes/improvements as outlined in the
 changelog:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346885

 Tag:
 https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_ALPHA_1
 Tag commit id: 9795452c58631d65e3b201682bc3c8343588710c

 The artifacts to be voted on are located as follows (r41591).
 Source release:
 https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-1/sources
 Convenience binaries:
 https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-1/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 4.0.0-alpha-1.

 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 4.0.0-alpha-1
 [ ]  0 I don't have a strong opinion about this, but I assume it's ok
 [ ] -1 Do not release Apache Groovy 4.0.0-alpha-1 because...

 Here is my vote:

 +1 (binding)

Re: [VOTE] Release Apache Groovy 3.0.6

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Sep 2020, at 0:04, Remko Popma  wrote:
> 
> 
> +1 Remko
> 
>> On Sat, Sep 26, 2020 at 6:19 PM Paul King  wrote:
>> 
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 3.0.6 release!
>> 
>> This release includes 72 bug fixes/improvements as outlined in the changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348621
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_6
>> Tag commit id: 6eb8bbbf62120a29cae04d3cdddf0e4e28954760
>> 
>> The artifacts to be voted on are located as follows (r41589).
>> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.6/sources
>> Convenience binaries: 
>> https://dist.apache.org/repos/dist/dev/groovy/3.0.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 3.0.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 3.0.6
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 3.0.6 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
>> 

Re: [VOTE] Release Apache Groovy 4.0.0-alpha-1

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 27 Sep 2020, at 0:04, Remko Popma  wrote:
> 
> 
> +1 Remko
> 
>> On Sat, Sep 26, 2020 at 10:19 PM Paul King  wrote:
>> 
>> Dear development community,
>> 
>> I am happy to start the VOTE thread for a Groovy 4.0.0-alpha-1 release!
>> 
>> This release includes 252 bug fixes/improvements as outlined in the 
>> changelog:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346885
>> 
>> Tag: 
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_ALPHA_1
>> Tag commit id: 9795452c58631d65e3b201682bc3c8343588710c
>> 
>> The artifacts to be voted on are located as follows (r41591).
>> Source release: 
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-1/sources
>> Convenience binaries: 
>> https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-1/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 4.0.0-alpha-1.
>> 
>> 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 4.0.0-alpha-1
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 4.0.0-alpha-1 because...
>> 
>> Here is my vote:
>> 
>> +1 (binding)
>> 

Re: [VOTE] Release Apache Groovy 3.0.5 (take 2)

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 20 Jul 2020, at 11:02, Guillaume Laforge  wrote:
> 
> 
> +1 (binding)
> 
> All tests green, and usual console smoke tests.
> 
> Guillaume
> 
> 
>> On Mon, Jul 20, 2020 at 12:43 AM Remko Popma  wrote:
>> +1
>> 
>>> On Sun, Jul 19, 2020 at 9:36 PM Paul King  wrote:
>>> 
>>> [Sorry for the glitch, let's try that again!]
>>> 
>>> Dear development community,
>>> 
>>> I am happy to start the VOTE thread for a Groovy 3.0.5 release!
>>> 
>>> This release includes 74 bug fixes/improvements as outlined in the 
>>> changelog:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348304
>>> 
>>> Tag: 
>>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_5
>>> Tag commit id: 0be35bb155d6188a6ccc727dea41646cefa706ac
>>> 
>>> The artifacts to be voted on are located as follows (r40558).
>>> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.5/sources
>>> Convenience binaries: 
>>> https://dist.apache.org/repos/dist/dev/groovy/3.0.5/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 3.0.5.
>>> 
>>> 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.5
>>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>>> [ ] -1 Do not release Apache Groovy 3.0.5 because...
>>> 
>>> Here is my vote:
>>> 
>>> +1 (binding)
>>> 
> 
> 
> -- 
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
> 
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge

Re: [VOTE] Release Apache Groovy 2.5.13

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, Jul 19, 2020 at 9:36 AM Daniel Sun  wrote:

> +1 (binding)
>
> Cheers,
> Daniel Sun
>
> On 2020/07/19 03:13:52, Paul King  wrote:
> > Dear development community,
> >
> > I am happy to start the VOTE thread for a Groovy 2.5.13 release!
> >
> > This release includes 39 bug fixes/improvements as outlined in the
> > changelog:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348305
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_13
> > Tag commit id: 0e6f3ac4a641d1ef387ce9eba96be1ebe917c27f
> >
> > The artifacts to be voted on are located as follows (r40553).
> > Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.13/sources
> > Convenience binaries:
> > https://dist.apache.org/repos/dist/dev/groovy/2.5.13/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.13.
> >
> > 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.13
> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 2.5.13 because...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
>

Re: [VOTE] Release Apache Groovy 2.4.20

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, Jul 19, 2020 at 9:39 AM Daniel Sun  wrote:

> +1 (binding)
>
> Cheers,
> Daniel Sun
>
> On 2020/07/18 23:46:43, Paul King  wrote:
> > Dear development community,
> >
> > I am happy to start the VOTE thread for a Groovy 2.4.20 release!
> >
> > This release includes a handful of tweaks to the documentation and 2 bug
> > fixes/improvements as outlined in the changelog:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12347640
> > (these were causing IllegalAccessError or impacting Eclipse integration)
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_20
> > Tag commit id: a21733c9e20b208a614f890fffb0dd42ab3650c7
> >
> > The artifacts to be voted on are located as follows (r40550).
> > Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.4.20/sources
> > Convenience binaries:
> > https://dist.apache.org/repos/dist/dev/groovy/2.4.20/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.4.20.
> >
> > 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.4.20
> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 2.4.20 because...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
>

Re: [VOTE] Release Apache Groovy 3.0.5

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Sun, Jul 19, 2020 at 9:34 AM Daniel Sun  wrote:

>
> +1 (binding)
>
> Here is the build scan report:
> https://gradle.com/s/6zvgwt2553twy
>
> The only one failing test is related to my poor network ( Fails to access
> https://raw.githubusercontent.com/apache/groovy/master/subprojects/groovy-ant/src/test-resources/org/codehaus/groovy/ant/GroovyTest1.groovy
> via network ), so I assume it should be OK.
>
> Also, the groovySh and groovyConsole works find for me too.
>
> Cheers,
> Daniel Sun
>
> On 2020/07/19 06:19:50, Paul King  wrote:
> > Dear development community,
> >
> > I am happy to start the VOTE thread for a Groovy 3.0.5 release!
> >
> > This release includes 74 bug fixes/improvements as outlined in the
> > changelog:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348304
> >
> > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_5
> > Tag commit id: 49e6a303f1144582544ef6a16b80f425db2990e5
> >
> > The artifacts to be voted on are located as follows (r40554).
> > Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.5/sources
> > Convenience binaries:
> > https://dist.apache.org/repos/dist/dev/groovy/3.0.5/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 3.0.5.
> >
> > 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.5
> > [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Groovy 3.0.5 because...
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
>

Re: Reproducible builds

[Andres Almiray]

Hi Paul,

The shadow [1] plugin can relocate and rename classes as well. I've seen it
in use at many places, jarjar not so much.
Shadow works with reproducible archive support as provided by Gradle.

Cheers,
Andres

[1] https://imperceptiblethoughts.com/shadow/
[2]
https://imperceptiblethoughts.com/shadow/configuration/reproducible-builds/

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Wed, Jul 8, 2020 at 9:27 AM Paul King  wrote:

>
> Hi everyone,
>
> I was going to do some initial work to make our builds reproducible[1]. I
> was basically going to turn on the Gradle support as per [2].
>
> Currently jarjar isn't enabled for reproducible support. There is another
> plugin[3] (doesn't seem very active) that we could use to repack after
> jarjar tasks are run. Although that looks doable, I notice that the
> jarjar github repo has been recently archived[4], so we might want to
> consider our other options in that space.
>
> This means (after we resolve the jarjar side of things) that if two folks
> on different operating systems and at different times build a distribution
> from the same tag, that they will get bit for bit the same artifacts.
>
> For now, the timestamps will be set to the Gradle default Jan 1980 value.
> Out of scope for now (but PRs welcome) will be:
> * adding support so that the timestamp can be specified (Maven has an
> option to do that[5])
> 
> * producing a ".buildinfo" file in the first instance as per [6]
>
> Cheers, Paul.
>
>
> [1] https://issues.apache.org/jira/browse/GROOVY-9628
> [2]
> https://docs.gradle.org/6.5/userguide/working_with_files.html#sec:reproducible_archives
>
> [3] https://github.com/Johni0702/gradle-reproducible-builds-plugin
> [4] https://github.com/pantsbuild/jarjar
> [5] https://maven.apache.org/guides/mini/guide-reproducible-builds.html
> [6] https://reproducible-builds.org/docs/jvm/
>
>
>
>
>

Re: More inclusive naming

[Andres Almiray]

+1 Agreed,

Aliases in 3.x (should we target 2.x if there's a 2.5.13?)
We know that Groovy 4.0 will break binary compatibility due to removal of
split packages. We can remove the old names in Groovy 4.0.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Jun 11, 2020 at 5:13 PM Guillaume Laforge 
wrote:

> +1, that's a great idea!
>
>
> On Thu, Jun 11, 2020 at 5:08 PM Cédric Champeau 
> wrote:
>
>> +1
>>
>> Le jeu. 11 juin 2020 à 16:56, Jeff Beck  a écrit :
>>
>>> I find those aliases easier to understand. So I think it's a great
>>> improvement.
>>>
>>> Jeff
>>>
>>> On Thu, Jun 11, 2020, 9:50 AM Paul King  wrote:
>>>
 Hi folks,

 Given recent world events, there are numerous projects that are taking
 the opportunity to use more inclusive terminology especially in names
 within APIs. E.g. getting rid of things like master/slave,
 blacklist/whitelist, etc. While I have never witnessed any racist behavior
 in the Groovy community, it seems worthwhile to be as inclusive as we can.
 I scanned our codebase and it seems that the only potential candidate we
 have for such a change would be in SecureASTCustomizer. But feel free to
 chime in if you think there are others.

 For backwards compatibility, I wouldn't propose to remove the old names
 in the first instance, just provide friendly aliases. We can deprecate
 and/or remove the current names later if we feel the need. Some example
 aliases could be something like:

 tokensWhitelist => allowedTokens
 staticStarImportsWhitelist => allowedStaticStarImports
 importsBlacklist => prohibitedImports (or disallowedImports)

 Thoughts?

 Cheers, Paul.


>
> --
> Guillaume Laforge
> Apache Groovy committer
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Twitter: @glaforge 
>

Re: [VOTE] Release Apache Groovy 3.0.4

[Andres Almiray]

+1 (binding)

Make it so.

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, May 18, 2020 at 12:15 PM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.4 release!
>
> This release includes 45 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348064
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_4
> Tag commit id: c501240548ae5b78e375f88932225b7ba5fe9737
>
> The artifacts to be voted on are located as follows (r39652).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.4/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.4/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 3.0.4.
>
> 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.4
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.4 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 2.5.12

[Andres Almiray]

+1 (binding)

All good to go!

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, May 18, 2020 at 12:31 PM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.12 release!
>
> This release includes 10 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12348065
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_12
> Tag commit id: 1b8add46a5481dc7e6f328e68560cfe48a431e6d
>
> The artifacts to be voted on are located as follows (r39653).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.12/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.12/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.12.
>
> 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.12
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.12 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 3.0.3

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Apr 7, 2020 at 8:45 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.3 release!
>
> This release includes 40 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12347743
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_3
> Tag commit id: c55f6b8340a11fcbe2da364acc2d4242c80a7654
>
> The artifacts to be voted on are located as follows (r38834).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.3/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.3/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 3.0.3.
>
> 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.3
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.3 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 2.5.11

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Apr 7, 2020 at 9:31 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.11 release!
>
> This release includes 6 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12347744
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_11
> Tag commit id: 165c939c87fbd46d391d9339eb004aad302387e0
>
> The artifacts to be voted on are located as follows (r38835).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.11/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.11/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.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 2.5.11
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.11 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 3.0.2 (take 3)

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 5 Mar 2020, at 12:23, Paul King  wrote:
> 
> 
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.2 release!
> This with the switch regression fixed.
> 
> This release includes 25 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346991
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_2
> Tag commit id: 0c4cdf57fadcc9045c25c2ddc7728893555da56b
> 
> The artifacts to be voted on are located as follows (r38398).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.2/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/3.0.2/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 3.0.2.
> 
> 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.2
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.2 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 
> 

Re: [VOTE] Release Apache Groovy 2.5.10

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Mar 3, 2020 at 2:35 PM Paul King  wrote:

> Here is the real content!
>
> 
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.10 release!
>
> This release includes 12 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346773
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_10
> Tag commit id: fb068ef1829a98bc989eb438fe3e299071c17b5d
>
> The artifacts to be voted on are located as follows (r38368).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.10/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.5.10/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.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 2.5.10
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.5.10 because...
>
> Here is my vote:
>
> +1 (binding)
>
> On Tue, Mar 3, 2020 at 11:33 PM Paul King  wrote:
>
>>
>>

Re: Groovy Devcon

[Andres Almiray]

Hi Paul,

Great idea! I’ll likely be present at Gr8conf but I’m unsure about ApacheCon 
NA. 

Best
Andres

Sent from my primitive tricorder

> On 3 Mar 2020, at 0:29, Paul King  wrote:
> 
> 
> 
> Hi everyone,
> 
> In the past, we have held various Groovydev conferences to get together 
> members of the core team and broader ecosystem to discuss roadmaps/direction, 
> and to brainstorm and hack. In the last couple of years, we have just done 
> some informal discussion sessions on the back of a few conferences, but I'd 
> like to have a more dedicated block of time if we can arrange it. We are all 
> busy, so I suspect the best way to make it happen is to piggy-back on to a 
> conference. Possible candidates are Gr8conf EU in early June or ApacheCon NA 
> in late September.
> If anyone could make either of those dates, let me know.
> 
> Cheers, Paul.
> 

Re: [VOTE] Release Apache Groovy 2.4.19

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 29 Feb 2020, at 4:33, Paul King  wrote:
> 
> 
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 2.4.19 release!
> We weren't planning another 2.4.X release and there aren't many changes but a 
> downstream dependency bug is impacting numerous users stuck on Groovy 2.4. So 
> this should fix things for impacted users.
> 
> This release includes 4 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346771
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_19
> Tag commit id: 10931efeab0b6d9f3cb0335ee3e647b6d7abfa78
> 
> The artifacts to be voted on are located as follows (r38334).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/2.4.19/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/2.4.19/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.4.19.
> 
> 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.4.19
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.4.19 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 
> 
>   Virus-free. www.avast.com

Re: [VOTE] Release Apache Groovy 3.0.1

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 14 Feb 2020, at 11:07, Paul King  wrote:
> 
> 
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.1 release!
> There was a glitch in the Groovy binaries in the 3.0.0 release so
> I thought it prudent to get this out sooner rather than later.
> 
> This release includes 10 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346968
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_1
> Tag commit id: 2b7163965105421072d495bde918c236fdd8fb7a
> 
> The artifacts to be voted on are located as follows (r38042).
> Source release: https://dist.apache.org/repos/dist/dev/groovy/3.0.1/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/3.0.1/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 3.0.1.
> 
> 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.1
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.1 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 

Re: [VOTE] Release Apache Groovy 3.0.0

[Andres Almiray]

+1 (binding)

Hooray!

Sent from my primitive tricorder

> On 8 Feb 2020, at 19:50, Daniel.Sun  wrote:
> 
> +1 (binding)
> 
> All tests pass on my local machine:
> https://scans.gradle.com/s/rntcuyeb4mtjc
> 
> Also, I built the binary distribution from the source distribution
> successfully:
> https://gradle.com/s/h25t4se4fqhra
> 
> At last, I ran smoke tests in the groovySh and groovyConsole of the newly
> built binary distribution, all of the smoke tests pass, too.
> 
> Cheers,
> Daniel.Sun
> 
> 
> 
> -
> Apache Groovy committer & PMC member 
> Blog: http://blog.sunlan.me 
> Twitter: @daniel_sun 
> 
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: [VOTE] Release Apache Groovy 3.0.0-rc-3

[Andres Almiray]

+1 (binding)

Sent from my primitive tricorder

> On 12 Jan 2020, at 1:12, Paul King  wrote:
> 
> 
> 
> Dear development community,
> 
> I am happy to start the VOTE thread for a Groovy 3.0.0-rc-3 release!
> 
> This release includes 26 bug fixes/improvements as outlined in the changelog:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346592
> 
> Tag: 
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_RC_3
> Tag commit id: 2b57d13c95da204e8883e2a50cc58658ab10abb2
> 
> The artifacts to be voted on are located as follows (r37572).
> Source release: 
> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-3/sources
> Convenience binaries: 
> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-3/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 3.0.0-rc-3.
> 
> 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.0-rc-3
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.0-rc-3 because...
> 
> Here is my vote:
> 
> +1 (binding)
> 

Re: [VOTE] Release Apache Groovy 2.5.9

[Andres Almiray]

+1 (binding)

On Sat, Jan 11, 2020 at 5:42 AM Daniel.Sun  wrote:

> +1 (binding)
>
> Cheers,
> Daniel.Sun
>
>
>
> -
> Apache Groovy committer & PMC member
> Blog: http://blog.sunlan.me
> Twitter: @daniel_sun
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: [VOTE] Release Apache Groovy 2.4.18

[Andres Almiray]

+1 (binding)


On Sat, Jan 11, 2020 at 4:14 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.4.18 bug fix release!
>
> This release includes 3 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12345496
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_4_18
> Tag commit id: ee00dd257711390ecac3c5a3823db428a9a72a26
>
> The artifacts to be voted on are located as follows (r37563).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/2.4.18/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/2.4.18/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.4.18.
>
> 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.4.18
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.4.18 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: [VOTE] Release Apache Groovy 3.0.0-rc-2

[Andres Almiray]

+1 (binding)

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Thu, Dec 5, 2019 at 6:41 AM Paul King  wrote:

>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 3.0.0-rc-2 release!
>
> This release includes 49 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12346448
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_RC_2
> Tag commit id: 642a19994e91f8c53ffc2136094f173f927c9676
>
> The artifacts to be voted on are located as follows (r37081).
> Source release:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-2/sources
> Convenience binaries:
> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-rc-2/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 3.0.0-rc-2.
>
> 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.0-rc-2
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 3.0.0-rc-2 because...
>
> Here is my vote:
>
> +1 (binding)
>
>

Re: Field order from traits

[Andres Almiray]

I need consistent field order to get around this problem ->
https://github.com/gradle/gradle/issues/11522

I'm aware that reflection does not guarantee order. I was under the
impression that the compiler would use the AST which would have the correct
order but that only works if the trait is compiled in the same session as
the target code. The compiler would be forced to use reflection if the
trait is found only in binary in the classpath. Anyway, I found a
workaround which is to encapsulate the fields on another type and have that
latter be injected by the trait.

Thanks.

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Dec 2, 2019 at 2:56 AM Jochen Theodorou  wrote:

> Hi Andres,
>
> I think your expectations are wrong. To understand why it is important I
> wonder though what you need it for
>
> bye Jochen
>
>
> On 01.12.19 19:02, Andres Almiray wrote:
> > Hello everyone,
> >
> > I've encountered a "problem" when using traits. Say you have a couple of
> > traits that define fileds in the following order
> >
> > @CompileStatic
> > trait CompartmentIdAwareTrait implements PathAware, ProjectAware {
> > @Internal
> > final Property compartmentId =
> project.objects.property(String)
> >
> > @Input
> > final Provider resolvedCompartmentId = stringProvider(
> > 'OCI_COMPARTMENT_ID',
> > 'oci.compartment.id <http://oci.compartment.id>',
> > getCompartmentId(),
> > project)
> > }
> >
> > and
> >
> > @CompileStatic
> > trait InstanceNameAwareTrait implements PathAware, ProjectAware {
> >  @Internal
> >  final Property instanceName =
> project.objects.property(String)
> >
> >  @Input
> >  final Provider resolvedInstanceName = stringProvider(
> >  'OCI_INSTANCE_NAME',
> >  'oci.instance.name <http://oci.instance.name>',
> >  getInstanceName(),
> >  project)
> > }
> >
> > As you can see there's a regular property field and a "resolved"
> > provider field. I expected these fields to be copied in definition
> > order, that is, resolved fields will always be second thus the reference
> > to their corresponding property field will work.
> >
> > However that's not the case. I'm compiling code with Groovy 2.5.8 (I
> > think that's the version used by Gradle 6.0.1) and I find the following
> > fields in the bytecode of the target class that applies the traits
> >
> >private final org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__resolvedInstanceName;
> >private final org.gradle.api.provider.Property
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__instanceName;
> >private final org.gradle.api.provider.Property
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__compartmentId;
> >private final org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__resolvedCompartmentId;
> >
> > The order of copied fields is not consistent either
> >
> >private final org.gradle.api.provider.Property
> > org_kordamp_gradle_plugin_oci_tasks_traits_VerboseAwareTrait__verbose;
> >private final org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_VerboseAwareTrait__resolvedVerbose;
> >private final
> > org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_UserDataFileAwareTrait__resolvedUserDataFile;
> >private final org.gradle.api.file.RegularFileProperty
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_UserDataFileAwareTrait__userDataFile;
> >private final org.gradle.api.file.RegularFileProperty
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_PublicKeyFileAwareTrait__publicKeyFile;
> >private final
> > org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_PublicKeyFileAwareTrait__resolvedPublicKeyFile;
> >private final org.gradle.api.provider.Provider
> >
> org_kordamp_gradle_plugin_oci_tasks_traits_ShapeAwareTrait__resolvedShape;
> >private final org.gradle.api.provider.Property
> > org_k

Field order from traits

[Andres Almiray]

Hello everyone,

I've encountered a "problem" when using traits. Say you have a couple of
traits that define fileds in the following order

@CompileStatic
trait CompartmentIdAwareTrait implements PathAware, ProjectAware {
   @Internal
   final Property compartmentId = project.objects.property(String)

   @Input
   final Provider resolvedCompartmentId = stringProvider(
   'OCI_COMPARTMENT_ID',
   'oci.compartment.id',
   getCompartmentId(),
   project)
}

and

@CompileStatic
trait InstanceNameAwareTrait implements PathAware, ProjectAware {
@Internal
final Property instanceName = project.objects.property(String)

@Input
final Provider resolvedInstanceName = stringProvider(
'OCI_INSTANCE_NAME',
'oci.instance.name',
getInstanceName(),
project)
}

As you can see there's a regular property field and a "resolved" provider
field. I expected these fields to be copied in definition order, that is,
resolved fields will always be second thus the reference to their
corresponding property field will work.

However that's not the case. I'm compiling code with Groovy 2.5.8 (I think
that's the version used by Gradle 6.0.1) and I find the following fields in
the bytecode of the target class that applies the traits

  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__resolvedInstanceName;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__instanceName;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__compartmentId;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__resolvedCompartmentId;

The order of copied fields is not consistent either

  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_VerboseAwareTrait__verbose;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_VerboseAwareTrait__resolvedVerbose;
  private final
org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_UserDataFileAwareTrait__resolvedUserDataFile;
  private final org.gradle.api.file.RegularFileProperty
org_kordamp_gradle_plugin_oci_tasks_traits_UserDataFileAwareTrait__userDataFile;
  private final org.gradle.api.file.RegularFileProperty
org_kordamp_gradle_plugin_oci_tasks_traits_PublicKeyFileAwareTrait__publicKeyFile;
  private final
org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_PublicKeyFileAwareTrait__resolvedPublicKeyFile;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_ShapeAwareTrait__resolvedShape;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_ShapeAwareTrait__shape;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_ImageAwareTrait__resolvedImage;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_ImageAwareTrait__image;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__resolvedInstanceName;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_InstanceNameAwareTrait__instanceName;
  private final org.gradle.api.provider.Property
org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__compartmentId;
  private final org.gradle.api.provider.Provider
org_kordamp_gradle_plugin_oci_tasks_traits_CompartmentIdAwareTrait__resolvedCompartmentId;

So I wonder if this is some bug or my expectations are wrong.

I expected fields to be copied in the same order as they were defined in
the trait.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.

Re: Upcoming releases

[Andres Almiray]

Hello there,

I spoke with Rémi Forax at Devoxx justa  few days ago regarding a message
sent to the Openjdk dev list related to Groovy/Gradle/ASM. Long story short
the toolchain is not updated because Groovy does not publish a release with
the latest ASM, which makes really hard to build projects with latest
OpenJDK early access builds because Gradle croaks.

A couple of ideas:
- push a Groovy release where the only change is an upgrade to latest ASM
release. In this way the Gradle team can test if any regressions occur
_only_ by ASM and not because we added something extra.
- stop shading ASM and use it as a regular dependency. Apparently we used
to shade ASM for valid reasons in the past, but now that we publish Groovy
as a BOM we may rely on regular dependencies.

I'm aware that any of these two changes do not constitute a change one
usually push during an RC cycle.

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Mon, Nov 11, 2019 at 7:22 AM Paul King  wrote:

>
> We plan to do a RC-2 release shortly (possibly next week) and it's
> probably also time for releases on other branches. The 2.5 branch has
> numerous fixes. The 2.4 branch is nominally unsupported but we have been
> asked to do another release to get some key fixes onto that branch. And an
> alpha of 4.0 is also on the cards.
>
> Please let us know if there are specific fixes you want for any of those
> releases.
>
> Cheers, Paul.
>
>

Re: ApacheCon NA 2020

[Andres Almiray]

Yay! Let ApacheCon be groovier :-)

Sent from my primitive tricorder

> On 7 Nov 2019, at 10:53, Paul King  wrote:
> 
> 
> 
> Hi all,
> 
> We currently have a day allocated to Groovy (and related technologies) for 
> ApacheCon 2020 NA (venue still to be determined). If there are lots of folks 
> interested in giving talks, we can ask for more slots. If folks can let me 
> know their interest I can pass that on to the conference organizers.
> 
> Cheers, Paul.
> 

Re: Apache Groovy Board Report [DRAFT]

[Andres Almiray]

Eric Milles was recently voted as committer. 

Sent from my primitive tricorder

> On Aug 13, 2019, at 09:52, Paul King  wrote:
> 
> Okay, obviously that should have said 13th not 3rd for TIOBE. I've fixed 
> already but other comments welcome.
> 
>> On Tue, Aug 13, 2019 at 5:50 PM Paul King  wrote:
>> 
>> Any feedback before I send this in?
>> 
>> Thanks, Paul.
>> 
>> --
>> 
>> ## Description:
>> Apache Groovy is responsible for the evolution and maintenance of the Groovy 
>> programming language. Groovy is a multi-faceted JVM programming language.
>> 
>> ## Issues:
>> There are no issues requiring board attention at this time.
>> 
>> Wrt the Maven Coordinate namespace: we are planning to move to
>> org.apache.groovy for Groovy 4 with alphas expected soon.
>> 
>> ## Membership Data:
>> Apache Groovy was founded 2015-11-18 (4 years ago)
>> There are currently 17 committers and 10 PMC members in this project.
>> Community changes, past quarter:
>> - No new PMC members. Last addition was Daniel Sun on 2019-05-06.
>> - No new committers. Last addition was Remko Popma on 2018-07-07.
>> A new committer has been invited and has accepted but the ICLA is
>> still pending. We anticipate including this in our next report.
>> 
>> ## Project Activity:
>> Recent releases:
>> 2.5.8 was released on Wed Aug 07 2019
>> 3.0.0-beta-2 was released on Mon Jul 08 2019
>> 3.0.0-beta-3 was released on Wed Aug 07 2019
>> 
>> This quarter, 327 commits were contributed from 9 contributors
>> including 5 non-committer contributors (1 new).
>> 
>> ## Community Health:
>> We recently did an assessment of health across commits,
>> contributors, issues resolved, releases and downloads
>> over the last 15 years including approx 4 yrs with Apache.
>> Commits and issues resolved have remained steady for most
>> of the life of the project. Releases dropped in 2016 while
>> we were becoming accustomed to the Apache Way but is now
>> inline with pre-Apache cadence. Number of contributors has
>> increased since joining Apache. Downloads have always
>> increased and continue to do so. Groovy artifacts have been
>> downloaded more than a quarter of a billion times since its inception.
>> 
>> According to the TIOBE index for this month, Apache Groovy
>> is the 3rd most popular programming language putting it ahead of:
>> Go (17), Swift (18), Perl (19), R (20), Scala (36) and Kotlin (45).
>>