FYI: I'm getting close to being able to stage this. One of the discoveries
I've made is that since merging grails-forge, we didn't properly verify the
grails-forge release in the M4. I now have this working as expected, but I
did have to open:
https://github.com/apache/grails-core/issues/14886
Go go go!
Den man. 7. jul. 2025 kl. 08.17 skrev Mattias Reichel <
mattias.reic...@gmail.com>:
> Yes!
> That would be terrific, thank you James!
>
> Den sön 6 juli 2025 23:54James Daugherty .invalid>
> skrev:
>
> > Hi Everyone,
> >
> > We have recently merged some significant, impactful changes.
Yes!
That would be terrific, thank you James!
Den sön 6 juli 2025 23:54James Daugherty
skrev:
> Hi Everyone,
>
> We have recently merged some significant, impactful changes. I've created
> a 7.0.0-M5 milestone in the issue tracker to track everything that should
> now be resolved:
>
> https://g
That would be great
Gianluca Sartori
--
https://dueuno.com
On Sun, 6 Jul 2025 at 23:54, James Daugherty
wrote:
> Hi Everyone,
>
> We have recently merged some significant, impactful changes. I've created
> a 7.0.0-M5 milestone in the issue tracker to track everything that should
> now be reso
This is a huge step forward. I would be totally ok doing an M5 vote this week.
> On Jul 6, 2025, at 5:54 PM, James Daugherty
> wrote:
>
> Hi Everyone,
>
> We have recently merged some significant, impactful changes. I've created
> a 7.0.0-M5 milestone in the issue tracker to track everything
