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
* Code Style as a separate Gradle Plugin - discussed moving our code style configuration to its own repository so all of our projects can adopt it's formatting decisions, including gradle buildSrc files - we agreed to proceed, so vote will need to happen for next steps * All Grails Github Action enhancements have been completed. We previously discussed these as a requirement for 7.0 release. - feedback on post-release changes: the release update enhancement should be configurable / optional. James D to follow-up with PR for this. * GitHub Release Settings for RC & Milestone versions - going forward, after the release of 7.0.0 we intend to leave milestone / RC builds as "pre-release". Only actual versions will transition from pre-release to release as a setting on the GitHub release. * Organization support has been added to grails-publish. We need to still adopt its usages throughout our projects. - James D to set up a meeting tomorrow @ same time as weekly dev meeting this week; meeting will train others on how to release. Søren, Mattias, & James F attend. * All TLP / Graduation related tickets have been completed across grails-github-actions, grails-gradle-publish, grails-redis, grails-quartz, grails-spring-security, & grails-core repositories. Special thanks to Søren for his hard work! * Are we in feature lock for Grails 7 and ready to release GA? - any changes to 7.0.0 must be backwards compatible - agreed to be feature locked * Grails Release Versions - agreement to do minor releases monthly as needed. Will treat releases as a monthly cut off to ensure timely, scheduled releases. -- follows the spring boot release cycle -- will break this rule if spring boot does to follow their lead - minor releases would have features, but not break changes. - hotfixes would be meant for security / bug fixes (no breaking changes) * GSP Performance PR - https://github.com/apache/grails-core/pull/15109 - Decided to go into 7.0.0. Gianluca has volunteered to do further testing in the next 24 hours to ensure backwards compatibility & test the performance fixes as part of his test suite. - logging was switched because of syntactic sugar (helps remove redundant statements and matches core) -- grails-core already includes slf4j and gsp includes grails-core -- spring boot uses slf4j -- spring framework uses commons - longer term we can re-address using commons if gsp becomes stand alone project * Dependency updates on plugins (redis, quartz, & spring security) - examples: https://github.com/orgs/apache/projects/487/views/2?sliceBy%5Bvalue%5D=grails%3A7.0.0&pane=issue&itemId=127418032&issue=apache%7Cgrails-spring-security%7C1160 - https://github.com/apache/grails-redis/issues/196 - https://github.com/apache/grails-quartz/issues/158 - decided to move forward with pom simplification - treating grails as a platform, and thus not listening those dependencies in the pom - James F to submit PRs * Søren requested feedback on two blog posts / articles for InfoQ / DZone. - goal is for the team to respond by next week's weekly meeting * James F discussed https://grails.apache.org consolidation - consolidation of docs, guides, and website - why consolidate: easier to find everything, consolidate analytics under analytics.apache.org, & SEO benefits from combining under Apache subdomain - now published from https://github.com/apache/grails-website -- currently 800k files and 19GB of data - docs will be the next item fully migrated & redirected -- James F sees this happening over the coming months. - order for subsequent migrations: -- legacy docs --- async --- gorm --- gsp --- testing --- views -- forge-ui will move to /forge or /start -- guides will move to /guides * Name / Description on grails-core poms - the poms have mixed usage of Apache Grails & Grails. Grails is the trademark so for now we decided to leave the grails-core framework published as "Grails" until trademark transferred & guidance given how to proceed. - forge will continue to use the Apache Grails labeling. - James F to follow-up * Standardized ISO-8601 json date conversions - https://github.com/apache/grails-core/pull/15121 - will merge into 7.0.0 after Mattias reviews * Removing @Autotimestamp Annotation - https://github.com/apache/grails-core/pull/15118 - will merge into 7.1.0 after branch creation * Groovy 4.0.29 has fix for Stackoverflow issue - will likely not be ready for 7.0.0 release, but users can update & we can release a hotfix after Groovy releases * https://github.com/gradle/gradle/pull/35218 - Groovy 3.0.25 / Gradle 8.14.4 - will bring Java 15 support (see https://issues.apache.org/jira/browse/GROOVY-11593) * Gradle 9 support - will likely come in Grails 8, may be backported to minor release after 7 *** Grails 7 Release *** Will likely call for a vote as soon as the last changes are merged. -James
