Grails Engineering Meeting Notes (12 03 2020)

Date: 12/03/2020

Attendees

CVE is being created that impacts both Groovy and Grails
- Groovy 2.5.14 is being updated to address it
- We know the fix for Grails and will be updating 4.1, 4.0, and 3.3 to patch it
  - The fix requires Java 7, so Grails 3.3 should be able to be updated without issue but there might be complications in the Travis build
Joint validation has been set up for Groovy 2.5.x on Grails
- groovy.ui.Console class has been changed in Groovy 2.5.14 and is a breaking change but I think it is safe to update it in Grails 4.0.6 as most users will not be directly using it in their application or plugin so the impact is very less.
Worked on bug fixes for testing support, Grails Core, and Micronaut Spring Configuration
Grails 4.0.6 needs an updated Micronaut Spring, but Micronaut Spring depends on a newer version of Spring than is supported in 4.0.x
- Ivan: We can do a patch release to an earlier release of Micronaut Spring that uses the appropriate version of Spring
- Ivan: It looks like 2.0.1 has the right version of spring, so we can branch and release there
Planning to release M3 of Grails 4.1 soon
May need some help in the coming weeks to test guides with 4.1 release
In addition to moving Grails Core to GitHub Actions, also planning on setting up GitHub Actions for GORM due to Travis slowing down
Issue in Grails that I would like to discuss with Bobby: https://github.com/agileorbit/grails-schwartz/issues/18
- He was unable to make it today, I will reach out to him in Slack

Puneet suggested that we decommission the Grails Jira instance.
- The group agreed this can safely be done

Iván suggested that we decommission the old Grails 2 portal
- The legacy plugin portal only applies for Grails 1 and 2
- There are multiple issues deploying it
- Turning this off will not break Grails 1 & 2 applications. This is just used to search plugins and find documentation which can be done using search engines
Puneet: I think we should document in the Wiki where the information for the plugins in the Grails 1 & 2 plugin portal can be located

Iván presented to the group the new environment and documentation to maintain it
We recently received credentials to deploy PWS environment to AWS
Iván submitted a PR to switch the build to deploy to AWS and also disables Travis
Iván: We need to create some subdomains and certificates for the deployments
- Jason: Please submit tickets to the system admins for that

Puneet reviewed issue (https://github.com/grails-plugins/grails-database-migration/issues/169)
Other meeting participants were not familiar enough with the issue to assist
Puneet stated he will look into it