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 Given that we have addressed a significant amount of license, disclaimer, and notice issues in almost every jar, my intent is to address the 2 affected jar files in the next release since the DISCLAIMER is still in our project and we are still in incubation. -James On Mon, Jul 7, 2025 at 2:53 AM Søren Berg Glasius <soe...@glasius.dk> wrote: > 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 <jdaughe...@jdresources.net > > .invalid> > > 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://github.com/apache/grails-core/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3Agrails%3A7.0.0-M5 > > > > > > > > > This email is to check if people are ok doing an M5 vote this week. > What > > > are people's thoughts? > > > > > > -James > > > > > > > > -- > > 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. >
