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 first ASF releases:
- grails-core - released 7.0.0-M4
- grails-redis - need to call a release for 5.0.0-M4
- grails-spring-security - need to call a release for 7.0.0-M4

* We discussed the semantics of calling a vote for dependent plugins. We
decided to call them together.

* A few outstanding groovy issues have been found for build
reproducibility:
- `@Delegate` can cause differences, a fix has been merged for groovy 4.0.28
- `@DelegateTo` can cause differences, a fix has been discussed on a side
branch, but not merged at this time.  James D is doing further testing with
Paul to decide how best to fix this.  This triggers differences primarily
on GormEntity.withCriteria { }

* SVN uploads in the CI pipeline are still blocked because the
credentails are saying access denied.  James D is following up with ASF
infra.

* Several people worked on the initial grails.apache.org website so we
could announce the grails milestone and we reviewed the site status:
- new download page: https://grails.staged.apache.org/download.html
- several tickets related to the site improvements:
-- https://github.com/apache/grails-static-website/issues/359 - download
links for M4
-- https://github.com/apache/grails-static-website/issues/357 - podling
checks
-- https://github.com/apache/grails-static-website/issues/356 - redirect
grails.org to grails.apache.org

* Based on the feedback & experience of the Grails milestone release, we
discussed further mono repo changes:
- merging grails-forge since the compile steps we provide are not that
clear.  If we don't merge grails-forge we would need to provide a build
script that only is ever called as part of verification / the source
distro.  We discussed how merging forge would work.  James D has a PR that
will clean-up the build so that the micronaut related functions do not
interfere with the Grails build.  He will start a separate discussion
thread on possible solutions.

- merge grails-spring-security; we discussed if it makes sense to merge. We
agreed to not merge it because they are separate projects and it would
complicate the core release process since it depends on the grails mail
plugin.

* we discussed the recent load issues on repository.apache.org.  ASF infra
will aggressively block you if you request an artifact that returns a 404.
Thus, we need to change our builds & generators to ensure only expected
artifacts are requested from RAO.

* we discussed the old build user and the progress being made to convert it
to priv...@grails.apache.org.  James F presented 2 options - removing the
old user or removing the newly created user.  We decided on removing the
new user and updating the old user's email to priv...@apache.org.

* We have a hard deadline to migrate the legacy org.grails coordinates due
to the maven central change on June 30th.  James F is going to prioritize
the old build user changes so we can continue to publish in the old
namespace as needed.

* Grails.org Domain & DNS migration is ongoing.  We are working with
infrastructure to switch them.

* We reviewed the outstanding project board tickets here:
https://github.com/orgs/apache/projects/487/views/2?sliceBy%5Bvalue%5D=grails%3A7.0.0-M4

-James

Reply via email to