You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by James Daugherty <jd...@jdresources.net> on 2025/07/27 22:06:49 UTC

[VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Hi Everyone,


The Apache Grails podling has voted to approve the release of Apache Grails
(incubating) Plugin - Spring Security 7.0.0-M5

As the incubation host, we now kindly request the Groovy PMC to review &
approve our initial ASF release.


Grails vote thread:
* https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw


Vote result thread:
* https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27

At a high level, this plugin is being updated to support the
recent Grails 7.0.0-M5 release. Further details of this release can be
found on the GitHub pre-release.

Please note that this vote will be dependent on the redis vote passing.

As far as reproducibility,
grails-spring-security has differences related to:
1. `@DelegateTo` fixed in Groovy 4.0.28
2. `@Delegate` fixed in Groovy 4.0.28
3. The views.properties file generated by the gsp compiler has
non-deterministic ordering (I've opened
https://github.com/apache/grails-core/issues/14930 to address in a
future release)
4. The acl plugin has closures names generated in different order

I've confirmed the functionality of these differences is the same and
will look into addressing these issues in the future.

Tags:
grails-spring-security:
https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354

The sources artifacts to be voted on are located as follows:
grails-spring-security (r38355):
https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/

Artifacts are signed with a key from the following file:
https://dist.apache.org/repos/dist/release/incubator/grails/KEYS

Please vote on releasing this package as:
Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5

Reminder on ASF release approval requirements:
https://www.apache.org/legal/release-policy.html#release-approval

Hints on validating checksums/signatures (but replace md5sum with
sha512sum):
https://www.apache.org/info/verification.html

The release process of these repositories, including verification, is
somewhat similar to grails-core which is documented at:
https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md

The vote is open for the next 72 hours.

[ ] +1 Release Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
[ ]  0 I don't have a strong opinion about this, but I assume it's ok
[ ] -1 Do not release Apache Grails (incubating) - Spring Security
Plugin 7.0.0-M5 because...

Re: [VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Posted by Søren Berg Glasius <so...@glasius.dk>.
+1 (binding)

Den lør. 2. aug. 2025 kl. 09.59 skrev Guillaume Laforge <glaforge@gmail.com
>:

> +1 (binding)
>
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud <https://cloud.google.com/>
>
>    - Blog: glaforge.dev
>    - X: @glaforge <http://twitter.com/glaforge>
>    - Bluesky: @glaforge.dev <https://bsky.app/profile/glaforge.dev>
>    - Mastodon: @glaforge@uwyn.net <http://%40glaforge@uwyn.net/>
>
>
> Le sam. 2 août 2025, 07:36, Sergio del Amo <se...@softamo.com> a
> écrit :
>
>> +1
>>
>> On 2 Aug 2025, at 04:46, Remko Popma <re...@gmail.com> wrote:
>>
>> +1
>>
>> On Tue, Jul 29, 2025 at 9:24 PM Paul King <pa...@asert.com.au> wrote:
>>
>>> +1 binding (paulk)
>>>
>>> I checked:
>>>
>>> * incubating in name
>>> * no unexpected binaries in distribution
>>> * LICENSE, NOTICE, DISCLAIMER files exist and appear correct
>>> * 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 noticed that LICENSE and NOTICE are in your rat excludes, they don't
>>> need to be and usually aren't (an easy fix for next time)
>>> * I locally (macOS) ran "etc/bin/verify.sh v7.0.0-M5" and I obtained the
>>> expected result
>>>
>>> Cheers, Paul.
>>>
>>> On Mon, Jul 28, 2025 at 8:07 AM James Daugherty <
>>> jdaugherty@jdresources.net> wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>>
>>>> The Apache Grails podling has voted to approve the release of Apache
>>>> Grails
>>>> (incubating) Plugin - Spring Security 7.0.0-M5
>>>>
>>>> As the incubation host, we now kindly request the Groovy PMC to review &
>>>> approve our initial ASF release.
>>>>
>>>>
>>>> Grails vote thread:
>>>> * https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw
>>>>
>>>>
>>>> Vote result thread:
>>>> * https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27
>>>>
>>>> At a high level, this plugin is being updated to support the
>>>> recent Grails 7.0.0-M5 release. Further details of this release can be
>>>> found on the GitHub pre-release.
>>>>
>>>> Please note that this vote will be dependent on the redis vote passing.
>>>>
>>>> As far as reproducibility,
>>>> grails-spring-security has differences related to:
>>>> 1. `@DelegateTo` fixed in Groovy 4.0.28
>>>> 2. `@Delegate` fixed in Groovy 4.0.28
>>>> 3. The views.properties file generated by the gsp compiler has
>>>> non-deterministic ordering (I've opened
>>>> https://github.com/apache/grails-core/issues/14930 to address in a
>>>> future release)
>>>> 4. The acl plugin has closures names generated in different order
>>>>
>>>> I've confirmed the functionality of these differences is the same and
>>>> will look into addressing these issues in the future.
>>>>
>>>> Tags:
>>>> grails-spring-security:
>>>> https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
>>>> Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354
>>>>
>>>> The sources artifacts to be voted on are located as follows:
>>>> grails-spring-security (r38355):
>>>>
>>>> https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/
>>>>
>>>> Artifacts are signed with a key from the following file:
>>>> https://dist.apache.org/repos/dist/release/incubator/grails/KEYS
>>>>
>>>> Please vote on releasing this package as:
>>>> Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>>>>
>>>> Reminder on ASF release approval requirements:
>>>> https://www.apache.org/legal/release-policy.html#release-approval
>>>>
>>>> Hints on validating checksums/signatures (but replace md5sum with
>>>> sha512sum):
>>>> https://www.apache.org/info/verification.html
>>>>
>>>> The release process of these repositories, including verification, is
>>>> somewhat similar to grails-core which is documented at:
>>>> https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md
>>>>
>>>> The vote is open for the next 72 hours.
>>>>
>>>> [ ] +1 Release Apache Grails (incubating) - Spring Security Plugin
>>>> 7.0.0-M5
>>>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>>>> [ ] -1 Do not release Apache Grails (incubating) - Spring Security
>>>> Plugin 7.0.0-M5 because...
>>>>
>>>
>>

-- 

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.

Re: [VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Posted by Guillaume Laforge <gl...@gmail.com>.
+1 (binding)

*Guillaume Laforge*
Apache Groovy committer
Developer Advocate @ Google Cloud <https://cloud.google.com/>

   - Blog: glaforge.dev
   - X: @glaforge <http://twitter.com/glaforge>
   - Bluesky: @glaforge.dev <https://bsky.app/profile/glaforge.dev>
   - Mastodon: @glaforge@uwyn.net <http://%40glaforge@uwyn.net/>


Le sam. 2 août 2025, 07:36, Sergio del Amo <se...@softamo.com> a
écrit :

> +1
>
> On 2 Aug 2025, at 04:46, Remko Popma <re...@gmail.com> wrote:
>
> +1
>
> On Tue, Jul 29, 2025 at 9:24 PM Paul King <pa...@asert.com.au> wrote:
>
>> +1 binding (paulk)
>>
>> I checked:
>>
>> * incubating in name
>> * no unexpected binaries in distribution
>> * LICENSE, NOTICE, DISCLAIMER files exist and appear correct
>> * 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 noticed that LICENSE and NOTICE are in your rat excludes, they don't
>> need to be and usually aren't (an easy fix for next time)
>> * I locally (macOS) ran "etc/bin/verify.sh v7.0.0-M5" and I obtained the
>> expected result
>>
>> Cheers, Paul.
>>
>> On Mon, Jul 28, 2025 at 8:07 AM James Daugherty <
>> jdaugherty@jdresources.net> wrote:
>>
>>> Hi Everyone,
>>>
>>>
>>> The Apache Grails podling has voted to approve the release of Apache
>>> Grails
>>> (incubating) Plugin - Spring Security 7.0.0-M5
>>>
>>> As the incubation host, we now kindly request the Groovy PMC to review &
>>> approve our initial ASF release.
>>>
>>>
>>> Grails vote thread:
>>> * https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw
>>>
>>>
>>> Vote result thread:
>>> * https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27
>>>
>>> At a high level, this plugin is being updated to support the
>>> recent Grails 7.0.0-M5 release. Further details of this release can be
>>> found on the GitHub pre-release.
>>>
>>> Please note that this vote will be dependent on the redis vote passing.
>>>
>>> As far as reproducibility,
>>> grails-spring-security has differences related to:
>>> 1. `@DelegateTo` fixed in Groovy 4.0.28
>>> 2. `@Delegate` fixed in Groovy 4.0.28
>>> 3. The views.properties file generated by the gsp compiler has
>>> non-deterministic ordering (I've opened
>>> https://github.com/apache/grails-core/issues/14930 to address in a
>>> future release)
>>> 4. The acl plugin has closures names generated in different order
>>>
>>> I've confirmed the functionality of these differences is the same and
>>> will look into addressing these issues in the future.
>>>
>>> Tags:
>>> grails-spring-security:
>>> https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
>>> Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354
>>>
>>> The sources artifacts to be voted on are located as follows:
>>> grails-spring-security (r38355):
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/
>>>
>>> Artifacts are signed with a key from the following file:
>>> https://dist.apache.org/repos/dist/release/incubator/grails/KEYS
>>>
>>> Please vote on releasing this package as:
>>> Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>>>
>>> Reminder on ASF release approval requirements:
>>> https://www.apache.org/legal/release-policy.html#release-approval
>>>
>>> Hints on validating checksums/signatures (but replace md5sum with
>>> sha512sum):
>>> https://www.apache.org/info/verification.html
>>>
>>> The release process of these repositories, including verification, is
>>> somewhat similar to grails-core which is documented at:
>>> https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md
>>>
>>> The vote is open for the next 72 hours.
>>>
>>> [ ] +1 Release Apache Grails (incubating) - Spring Security Plugin
>>> 7.0.0-M5
>>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>>> [ ] -1 Do not release Apache Grails (incubating) - Spring Security
>>> Plugin 7.0.0-M5 because...
>>>
>>
>

Re: [VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Posted by Sergio del Amo <se...@softamo.com>.
+1

> On 2 Aug 2025, at 04:46, Remko Popma <re...@gmail.com> wrote:
> 
> +1
> 
> On Tue, Jul 29, 2025 at 9:24 PM Paul King <paulk@asert.com.au <ma...@asert.com.au>> wrote:
>> +1 binding (paulk)
>> 
>> I checked:
>> 
>> * incubating in name
>> * no unexpected binaries in distribution
>> * LICENSE, NOTICE, DISCLAIMER files exist and appear correct
>> * 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 noticed that LICENSE and NOTICE are in your rat excludes, they don't need to be and usually aren't (an easy fix for next time)
>> * I locally (macOS) ran "etc/bin/verify.sh v7.0.0-M5" and I obtained the expected result
>> 
>> Cheers, Paul.
>> 
>> On Mon, Jul 28, 2025 at 8:07 AM James Daugherty <jdaugherty@jdresources.net <ma...@jdresources.net>> wrote:
>>> Hi Everyone,
>>> 
>>> 
>>> The Apache Grails podling has voted to approve the release of Apache Grails
>>> (incubating) Plugin - Spring Security 7.0.0-M5
>>> 
>>> As the incubation host, we now kindly request the Groovy PMC to review &
>>> approve our initial ASF release.
>>> 
>>> 
>>> Grails vote thread:
>>> * https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw
>>> 
>>> 
>>> Vote result thread:
>>> * https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27
>>> 
>>> At a high level, this plugin is being updated to support the
>>> recent Grails 7.0.0-M5 release. Further details of this release can be
>>> found on the GitHub pre-release.
>>> 
>>> Please note that this vote will be dependent on the redis vote passing.
>>> 
>>> As far as reproducibility,
>>> grails-spring-security has differences related to:
>>> 1. `@DelegateTo` fixed in Groovy 4.0.28
>>> 2. `@Delegate` fixed in Groovy 4.0.28
>>> 3. The views.properties file generated by the gsp compiler has
>>> non-deterministic ordering (I've opened
>>> https://github.com/apache/grails-core/issues/14930 to address in a
>>> future release)
>>> 4. The acl plugin has closures names generated in different order
>>> 
>>> I've confirmed the functionality of these differences is the same and
>>> will look into addressing these issues in the future.
>>> 
>>> Tags:
>>> grails-spring-security:
>>> https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
>>> Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354
>>> 
>>> The sources artifacts to be voted on are located as follows:
>>> grails-spring-security (r38355):
>>> https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/
>>> 
>>> Artifacts are signed with a key from the following file:
>>> https://dist.apache.org/repos/dist/release/incubator/grails/KEYS
>>> 
>>> Please vote on releasing this package as:
>>> Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>>> 
>>> Reminder on ASF release approval requirements:
>>> https://www.apache.org/legal/release-policy.html#release-approval
>>> 
>>> Hints on validating checksums/signatures (but replace md5sum with
>>> sha512sum):
>>> https://www.apache.org/info/verification.html
>>> 
>>> The release process of these repositories, including verification, is
>>> somewhat similar to grails-core which is documented at:
>>> https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md
>>> 
>>> The vote is open for the next 72 hours.
>>> 
>>> [ ] +1 Release Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>>> [ ] -1 Do not release Apache Grails (incubating) - Spring Security
>>> Plugin 7.0.0-M5 because...

Re: [VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Posted by Remko Popma <re...@gmail.com>.
+1

On Tue, Jul 29, 2025 at 9:24 PM Paul King <pa...@asert.com.au> wrote:

> +1 binding (paulk)
>
> I checked:
>
> * incubating in name
> * no unexpected binaries in distribution
> * LICENSE, NOTICE, DISCLAIMER files exist and appear correct
> * 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 noticed that LICENSE and NOTICE are in your rat excludes, they don't
> need to be and usually aren't (an easy fix for next time)
> * I locally (macOS) ran "etc/bin/verify.sh v7.0.0-M5" and I obtained the
> expected result
>
> Cheers, Paul.
>
> On Mon, Jul 28, 2025 at 8:07 AM James Daugherty <
> jdaugherty@jdresources.net> wrote:
>
>> Hi Everyone,
>>
>>
>> The Apache Grails podling has voted to approve the release of Apache
>> Grails
>> (incubating) Plugin - Spring Security 7.0.0-M5
>>
>> As the incubation host, we now kindly request the Groovy PMC to review &
>> approve our initial ASF release.
>>
>>
>> Grails vote thread:
>> * https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw
>>
>>
>> Vote result thread:
>> * https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27
>>
>> At a high level, this plugin is being updated to support the
>> recent Grails 7.0.0-M5 release. Further details of this release can be
>> found on the GitHub pre-release.
>>
>> Please note that this vote will be dependent on the redis vote passing.
>>
>> As far as reproducibility,
>> grails-spring-security has differences related to:
>> 1. `@DelegateTo` fixed in Groovy 4.0.28
>> 2. `@Delegate` fixed in Groovy 4.0.28
>> 3. The views.properties file generated by the gsp compiler has
>> non-deterministic ordering (I've opened
>> https://github.com/apache/grails-core/issues/14930 to address in a
>> future release)
>> 4. The acl plugin has closures names generated in different order
>>
>> I've confirmed the functionality of these differences is the same and
>> will look into addressing these issues in the future.
>>
>> Tags:
>> grails-spring-security:
>> https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
>> Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354
>>
>> The sources artifacts to be voted on are located as follows:
>> grails-spring-security (r38355):
>>
>> https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/
>>
>> Artifacts are signed with a key from the following file:
>> https://dist.apache.org/repos/dist/release/incubator/grails/KEYS
>>
>> Please vote on releasing this package as:
>> Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>>
>> Reminder on ASF release approval requirements:
>> https://www.apache.org/legal/release-policy.html#release-approval
>>
>> Hints on validating checksums/signatures (but replace md5sum with
>> sha512sum):
>> https://www.apache.org/info/verification.html
>>
>> The release process of these repositories, including verification, is
>> somewhat similar to grails-core which is documented at:
>> https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md
>>
>> The vote is open for the next 72 hours.
>>
>> [ ] +1 Release Apache Grails (incubating) - Spring Security Plugin
>> 7.0.0-M5
>> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Grails (incubating) - Spring Security
>> Plugin 7.0.0-M5 because...
>>
>

Re: [VOTE] Release Apache Grails (incubating) Plugin - Spring Security 7.0.0-M5

Posted by Paul King <pa...@asert.com.au>.
+1 binding (paulk)

I checked:

* incubating in name
* no unexpected binaries in distribution
* LICENSE, NOTICE, DISCLAIMER files exist and appear correct
* 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 noticed that LICENSE and NOTICE are in your rat excludes, they don't
need to be and usually aren't (an easy fix for next time)
* I locally (macOS) ran "etc/bin/verify.sh v7.0.0-M5" and I obtained the
expected result

Cheers, Paul.

On Mon, Jul 28, 2025 at 8:07 AM James Daugherty <jd...@jdresources.net>
wrote:

> Hi Everyone,
>
>
> The Apache Grails podling has voted to approve the release of Apache Grails
> (incubating) Plugin - Spring Security 7.0.0-M5
>
> As the incubation host, we now kindly request the Groovy PMC to review &
> approve our initial ASF release.
>
>
> Grails vote thread:
> * https://lists.apache.org/thread/vymkgbqmgojkwfklnjyy8h4vyz629vnw
>
>
> Vote result thread:
> * https://lists.apache.org/thread/h46185g46z7c8hlts80jzn4ftw5f1h27
>
> At a high level, this plugin is being updated to support the
> recent Grails 7.0.0-M5 release. Further details of this release can be
> found on the GitHub pre-release.
>
> Please note that this vote will be dependent on the redis vote passing.
>
> As far as reproducibility,
> grails-spring-security has differences related to:
> 1. `@DelegateTo` fixed in Groovy 4.0.28
> 2. `@Delegate` fixed in Groovy 4.0.28
> 3. The views.properties file generated by the gsp compiler has
> non-deterministic ordering (I've opened
> https://github.com/apache/grails-core/issues/14930 to address in a
> future release)
> 4. The acl plugin has closures names generated in different order
>
> I've confirmed the functionality of these differences is the same and
> will look into addressing these issues in the future.
>
> Tags:
> grails-spring-security:
> https://github.com/apache/grails-spring-security/releases/tag/v7.0.0-M5
> Tag commit id: 71a1b96a72b6952cd75be266f1fc86884012f354
>
> The sources artifacts to be voted on are located as follows:
> grails-spring-security (r38355):
>
> https://dist.apache.org/repos/dist/dev/incubator/grails/spring-security/7.0.0-M5/sources/
>
> Artifacts are signed with a key from the following file:
> https://dist.apache.org/repos/dist/release/incubator/grails/KEYS
>
> Please vote on releasing this package as:
> Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
>
> Reminder on ASF release approval requirements:
> https://www.apache.org/legal/release-policy.html#release-approval
>
> Hints on validating checksums/signatures (but replace md5sum with
> sha512sum):
> https://www.apache.org/info/verification.html
>
> The release process of these repositories, including verification, is
> somewhat similar to grails-core which is documented at:
> https://github.com/apache/grails-core/blob/7.0.x/RELEASE.md
>
> The vote is open for the next 72 hours.
>
> [ ] +1 Release Apache Grails (incubating) - Spring Security Plugin 7.0.0-M5
> [ ]  0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Grails (incubating) - Spring Security
> Plugin 7.0.0-M5 because...
>