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

Per Nyfelt <[email protected]>
Newsgroups gmane.comp.lang.groovy.devel
Message-ID <CAOAt0KR3d_j_D88CJdxhiPp-qcd2X-1A+fT_fabB+htqnt5WDQ@mail.gmail.com>
+1 (nb)

On Tue, 5 Aug 2025 at 10:34, Søren Berg Glasius <soeren-Kc6N1ySXURF/[email protected]> wrote:

> +1 (binding)
>
> Den man. 4. aug. 2025 kl. 20.25 skrev Milles, Eric (TR Technology) via dev
> <dev-GSC0n/0aZo1d/SJB6HiN2Ni2O/[email protected]>:
>
>> +1 (binding)
>> ------------------------------
>> *From:* Paul King <[email protected]>
>> *Sent:* Sunday, August 3, 2025 4:54 AM
>> *To:* Groovy_Developers <dev-GSC0n/0aZo1d/SJB6HiN2Ni2O/[email protected]>
>> *Subject:* [EXT] [VOTE] Release Apache Groovy 5.0.0-rc-1
>>
>> *External Email:* Use caution with links and attachments.
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 5.0.0-rc-1 release!
>>
>> This release includes 8 bug fixes/improvements as outlined in the
>> changelog:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12356146
>> <https://urldefense.com/v3/__https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12356146__;!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yIbfKrBgA$>
>>
>> Tag:
>> https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_RC_1
>> <https://urldefense.com/v3/__https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs*tags*GROOVY_5_0_0_RC_1__;Ly8!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yKsjXA9YQ$>
>> Tag commit id: c27086db039981ea28695d008e944086029f0408
>>
>> The artifacts to be voted on are located as follows (r78528).
>> Source release:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-rc-1/sources
>> <https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/groovy/5.0.0-rc-1/sources__;!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yKLiN7ltg$>
>> Convenience binaries:
>> https://dist.apache.org/repos/dist/dev/groovy/5.0.0-rc-1/distribution
>> <https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/groovy/5.0.0-rc-1/distribution__;!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yK6lKIwWA$>
>>
>> Release artifacts are signed with a key from the following file:
>> https://dist.apache.org/repos/dist/release/groovy/KEYS
>> <https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/groovy/KEYS__;!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yK-xgLtnA$>
>>
>> Please vote on releasing this package as Apache Groovy 5.0.0-rc-1.
>>
>> Reminder on ASF release approval requirements for PMC members:
>> http://www.apache.org/legal/release-policy.html#release-approval
>> <https://urldefense.com/v3/__http://www.apache.org/legal/release-policy.html*release-approval__;Iw!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yLGukzSow$>
>> Hints on validating checksums/signatures (but replace md5sum with
>> sha256sum):
>> https://www.apache.org/info/verification.html
>> <https://urldefense.com/v3/__https://www.apache.org/info/verification.html__;!!GFN0sa3rsbfR8OLyAw!ZwJYLWiKMN3Tzv-0Gx3OUlUatnn_9weqlr_vKpDWNjKvj-lpHVnGnKC6jXO7P86asYauw5V09rzn6yKT3sCEnw$>
>>
>> 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-rc-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-rc-1 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>> Cheers, Paul.
>>
>>
>
> --
>
> 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.
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.