We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.google.com/her-tjpt-xmf
Grails Micronaut Support * future versions require Java 21 > * still no champion in the community * Nate offered to help write a guide for moving from Micronaut -> Spring http client (HttpExchange starter makes this seamless) * Spring Boot 4 - came out in Nov, if Grails had released in Dec would been blocked by Micronaut - this isn't an issue for 4, but for 5 we may have to divest / separate micronaut - divesting does not mean spearating from mono repo * TODO: Add a note to the upgrade guie of Grails 8: micronaut support may be dropped in the future unless a champion can be found to assist on the development side. Spring Boot 4 * Outstanding issues - micronaut (requires java 21) - ensure tests pass Minimum Java Version for Grails 8 * 21 vs 17 debate * Java 17 support is set to expire for some vendors in 2027 (others in 2029) & Grails 8 support is expected to last through 2027. By adopting a min of 21, we ensure a supported JVM for the life of Grails 8 * consulted graphs of adoption * decided to adopt 21 as a minute 7.1 Release Status * Outstanding PRs - Bug Fix - mergeTestReports - https://github.com/apache/grails-core/pull/15563 - Bug Fix - Stacktrace filtering - https://github.com/apache/grails-core/pull/15564 - Feature - flashMessages - https://github.com/apache/grails-core/pull/15560 * Decided to have a 3 day cut off for any changes to 7.1. We will call for a vote within the week * Discussed future feature complete cut off dates as a requirement for releases. 8.1 will be the first release with that requirement. Mailmap Issue * Infrastructure has denied our private repo request for mailmap - deemed the request as 'unreasonable', we need to decide how to proceed. * For now, use an external process to store the file & revisit this later IntelliJ Plugin * We need to decide the future of the Grails IntelliJ plugin, 2 options: - Option 1 - Open Source under JetBrains Stewardship - Option 2 - Donation to the ASF for us to maintain * In either case, they have offered a limited time support for the transition period * We need to vote on this issue. Detailed Option info is below. IntelliJ Plugin - Option 1 * The plugin is open-sourced under the Apache 2.0 license and moved to the JetBrains intellij-obsolete-plugins repository (https://github.com/JetBrains/intellij-obsolete-plugins/tree/master/grails). Yann on their team has already begun this work, though some pieces are still outstanding. * A note on the repository name - it sounds more alarming than it is. Plugins in this repo are still built and released by JetBrains, and the team does periodically fix issues caused by breaking changes to the IntelliJ Plugin API. Key considerations: • Opens the plugin to community contributions, which has always been a need for us • JetBrains continues to handle builds and releases • JetBrains controls PR merges and release scheduling • JetBrains would provide reduced or no end-user support for the plugin • Grails Team support from JetBrains would be available (for reference, Apache Kafka received 8 hours/week for 6 months) IntelliJ Plugin - Option 2 JetBrains officially donates the plugin to ASF under the Apache Grails project. The Grails team would maintain the plugin, manage PRs, and handle releases independently. Key considerations: • Full control over the plugin's development and release cycle • We would be responsible for addressing IntelliJ Plugin API breakage (with potentially limited JetBrains assistance) • JetBrains would provide reduced or no end-user support for the plugin • Same transitional support offer as Option B (Kafka precedent: 8 hours/week for 6 months) Hibernate 7 * reviews waiting until Spring Boot 4 PR merged * Outstanding items to review - functionality - liquibase import (licensing requirements) - functional tests differences * For the PR on having all test projects run both hibernate 5 & 7: - Change will break gradle caching - Change is concerning because hibernate is not a single library (it's a chain of dependencies). Previously, we've only done this for sitemesh where it's a limited set of dependencies. - Reason to run all functional tests was to expand coverage, we could expand the hibernate specific functions tests instead. - Proposal to defer merge to 8.0.0-M2; agreement - The real concern is the PR identified real differences that need to be addressed (see comment https://github.com/apache/grails-core/pull/15561#issuecomment-4200976102) We need to make sure none of these are real differences / undocumented breaking changes. Walter to investigate. Indy Discussion * Not disabled on grails itself at this time * Proposal to disable for Grails 8 if we stay with Groovy 4 * Will revisit this discussion in future meetings
