M4 target was 7/22, it being early without 
https://lists.apache.org/thread/nq8f7yqtfp13wjbckkjxt1y82lrwkjq2 address, 
really caught me off guard.

2. Release 8.0.0-M4 by Wednesday (July 22) next week
- would include the undertow support + reproducible fixes + cli split
- last release of new features or breaking changes

If we are committed to getting some form of Grails 7 plugin in Grails 8 
backwards compatibility in RC1 or M5, I will be willing to change my vote to 0.

https://github.com/apache/grails-core/pull/16011 - is being updated right now 
to hopefully somewhere closer to a comprise.  

I think the number of hours and days of week we have worked on this as 
volunteers was historically unsustainable and is not something I have been able 
to maintain this year and will not be doing going forward.  72 hour turn around 
is the ASF expectation and that's what I will try to do.   Many time sooner, 
but I can't look at Apache Grails every day of the month.   

James

On 2026/07/21 13:29:06 James Fredley wrote:
> I am a -1 until we figure out a path for end users that does not require them 
> waiting on plugins to be re-released to use plugin commands in Grails 8.  
> Grails 7 is EOL and users have to move to Grails 8 basically upon release, 
> let's not break their ability to use Plugin Commands from the existing 
> already published Grails 7 plugins, if we do not have to.  
> 
> https://github.com/apache/grails-core/pull/15948 was merged before a path was 
> identified and we only addressed 1 of 4 paths that provide commands.
> 
> https://github.com/apache/grails-core/pull/16011 - provides a path, we can 
> debate that path, but I am firm that it should be the default for the reason 
> in the first paragraph.  Let's not hurt the framework.  
>  
> James
> 
> On 2026/07/21 09:35:43 Mattias Reichel wrote:
> > Hi Everyone,
> > I am happy to start the VOTE thread to release Apache Grails 8.0.0-M4!
> > 
> > Release notes for the release are here:
> > https://github.com/apache/grails-core/releases/tag/v8.0.0-M4
> > 
> > The tag for this release is:
> > https://github.com/apache/grails-core/releases/tag/v8.0.0-M4
> > 
> > Tag commit id: cb35496301c5423a557034394ce814dc1e1a36fa
> > 
> > The artifacts to be voted on are located as follows (r86111):
> > Source release:
> > https://dist.apache.org/repos/dist/dev/grails/core/8.0.0-M4/sources
> > Binary distributions:
> > https://dist.apache.org/repos/dist/dev/grails/core/8.0.0-M4/distribution
> > 
> > Release artifacts are signed with a key from the following file:
> > https://dist.apache.org/repos/dist/release/grails/KEYS
> > 
> > Please vote on releasing this package as: Apache Grails 8.0.0-M4.
> > 
> > Reminder on ASF release approval requirements for PMC members:
> > 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
> > 
> > Details of our release process are documented at:
> > https://github.com/apache/grails-core/blob/HEAD/RELEASE.md
> > 
> > As a reminder, most of our tools support an env `GRAILS_REPO_URL` so
> > that the tools can work with staged artefacts. Set it to the staging
> > repo like this: `export
> > GRAILS_REPO_URL=https://repository.apache.org/content/groups/staging`
> > 
> > The vote is open for a minimum of 72 hours and passes if a majority of at 
> > least
> > three +1 PMC votes are cast.
> > 
> > [ ] +1 Release Apache Grails 8.0.0-M4
> > [ ] 0 I don't have a strong opinion about this, but I assume it's ok
> > [ ] -1 Do not release Apache Grails 8.0.0-M4 because...
> > 
> > Here is my vote:
> > +1 (binding)
> > 
> 

Reply via email to