Sorry, wrong list. I'll resend in the correct place.

On Sun, Jun 15, 2025 at 8:56 PM Paul King <pa...@asert.com.au> wrote:

> Carrying forward my vote from the grails list:
>
> +1 paulk (binding)
>
> I checked (both plugins): * incubating in name * no unexpected binaries in
> distribution * LICENSE, NOTICE, DISCLAIMER files exist and appear correct *
> NOTICE file for security can be slightly reduced (I created a PR to improve
> this for the next release) * checked signatures and checksums (manually and
> see below) * bootstrapped gradlew (manually and see below) * checked rat
> (manually and see below; must be done before next step) * I locally (macOS)
> ran "etc/bin/verify.sh" and obtained currently expected results (details
> below) [results for security plugin which I believe show the known ordering
> issues but otherwise good] grails-spring-security> mkdir downloads
> grails-spring-security> etc/bin/verify.sh v7.0.0-M4 downloads ... ❌
> Differences Found ❌ [NOTE: due to known ordering issues]
> acl-plugin-7.0.0-M4.jar core-plugin-7.0.0-M4.jar oauth2-plugin-7.0.0-M4.jar
> ui-plugin-7.0.0-M4.jar [results for redis plugin with I believe one bogus
> false positive message but otherwise good] grails-redis> mkdir downloads
> grails-redis> etc/bin/verify.sh v5.0.0-M4 downloads ... ✅ No differences
> remain for grails-redis-5.0.0-M4-sources.jar. Removing from diff.txt. mv:
> cannot stat 'diff_purged.txt': No such file or directory ❌ Verification
> failed. ❌ [NOTE: bogus, No differences remain above is the key part]
> Cheers, Paul.
>
> On Sun, Jun 15, 2025 at 8:33 PM James Daugherty
> <jdaughe...@jdresources.net.invalid> wrote:
>
>> Hi Everyone,
>>
>>
>> The vote for releasing Apache Grails (incubating) Plugins
>> - Spring Security 7.0.0-M4 & Redis 5.0.0-M4[1] has passed.
>>
>>
>> The vote has passed with SEVEN +1 binding votes.  There was ONE +1
>> non-binding vote.
>>
>>
>> I will proceed with requesting approval from the Groovy PMC.
>>
>>
>> [1] https://lists.apache.org/thread/3o7qs2bhrly7ykxsdcbzb3k4q1zrdco1
>>
>

Reply via email to