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
* We discussed the release of 7.0.0-M4 - Grails seems to be a guinea pig for the releasing with GitHub workflows due to the various configuration delays - grails-forge is currently separate from grails-core, but it will always be released as part of the grails release process because of the delegating cli / forge being a requirement. - we have an ETA of 1 week prior to the milestone vote - The voting process will be first Grails podling PPMC votes on dev@grails.apache.org - 72 hours and then then Groovy PMC votes on d...@groovy.apache.org - 72 hours * Reviewed the Grails 7 Github Project Board by milestone: - https://github.com/orgs/apache/projects/487/views/2?sliceBy%5Bvalue%5D=grails%3A7.0.0-M4 - James D gave a summary of the reproducible builds ticket, and how it's been an ongoing effort. -- Highlights: - grails-forge will no longer use graalvm native builds due to lack of support in JDK 17 for reproducible builds, we moved back to a jar dist - Changes to grails-core for reproducibility include: -- AST transformations & confirming stable execution orders -- groovydoc updates to be consistent -- For the grails-core artifacts, there are 290 artifacts, with Groovy 4.0.27 only 2 have differences. 1 is a byte code only difference (false positive) and the other is an `@Delegate` issue that James D will open a groovy PR for -- build is now fully parallel, cacheable, & lazy -- the large amount of build changes will affect end user grails apps, and they may have to update their build files depending on how they use gradle -- we have changed grails-core over from a remote bom download to a local ( eliminated the spring dependency management plugin inside of core ) due to inconsistencies that kept being found -- the project mergers revealed the original tests weren't being run consistently, and these have been addressed as part of a wider repo merge * GitHub Pages to use HTTPS provided by GitHub instead of Cloudflare - https://github.com/apache/grails-core/issues/14731 - https://issues.apache.org/jira/browse/INFRA-26707 After those, we have the following remaining: ge.grails.org. 1 IN CNAME hosted-ge-grails.gradle.com. ; cf_tags=cf-proxied:true Is there an alternate URL for ge.grails.org using a Develocity https cert. The cname points to hosted-ge-grails.gradle.com which has a cert for *. grdev.net so that URL is mismatched to the cert. Or alternatively can ge.grails.org be configured to generate and use an https cert for ge.grails.org? latest.grails.org. 1 IN CNAME ghs.googlehosted.com. ; cf_tags=cf-proxied:true next.grails.org. 1 IN CNAME ghs.googlehosted.com. ; cf_tags=cf-proxied:true prev.grails.org. 1 IN CNAME ghs.googlehosted.com. ; cf_tags=cf-proxied:true prev-snapshot.grails.org. 1 IN CNAME ghs.googlehosted.com. ; cf_tags=cf-proxied:true snapshot.grails.org. 1 IN CNAME ghs.googlehosted.com. ; cf_tags=cf-proxied:true repo.grails.org. 1 IN CNAME grails.jfrog.org. ; cf_tags=cf-proxied:true grails.jfrog.io is another hostname for this instance * We reviewed the CLI changes, 7.0 now has: - delegating CLI - wrapper that should be forward compatible - grails-shell-cli - grails-forge-cli * Discussed Hibernate 5, 6, & 7 - recap of previous notes: https://github.com/apache/grails-core/discussions/13521#discussioncomment-12451797 - Grails 7 will likely be hibernate 5.6 jakarta at launch and add 6.6 as an option after launch - Grails 8 could be hibernate 6.6 and 7, and a small chance on 5.6 based on status on hibernate 5.6 and 7 * grails-doc - massive updates have been made to the Grails documentation to try to modernize it - we have started automating parts of it like generating the included Versions - Still need substantial contributions to update - several existing tickets here: https://github.com/apache/grails-core/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22relates-to%3A%20documentation%22 *grails starters - we revisited single line dependencies to start a grails app for easier adoption - Grails-dependencies would be a potential starting point - we will expand on this longer term * grails-module files are now correctly generated - POM files historically were usually correct, but module json files were not due to manual POM file manipulation. Going forward this should be correct to allow for the usage of platform() instead of the Spring Dependency Management plugin * We discussed the grails-plugin best practices and how we need to expand the grails guide to fill in the absence of a modern Grails book. -James
