Hi Everyone,
We meet every week via a google meeting. Since that meeting does not occur
over the dev mailing list, I intend to summarize the results of that
meeting going forward to facilitate historical preservation & further
discussion. If anyone would like to join this meeting, please let us know.
The notes for this week follow.
- We discussed several apache transition related topics:
- How reviews will take place on the grails project. Please see the
email entitled `Change Review Proposal` for further details.
- We intend to work on a transition plan after the repository
transfers. This plan will be reflected in either a wiki or ticket
process. Mattias suggested we use the ticket process so the current plan
is to use tickets to capture action items.
- The repositories transferred to apache will require the prefix
`grails-`. We discussed what to do with projects that do not have this
project and have decided the following:
- rename gorm implementations (repos) to have ‘grails-data-’ prefix
- rename repo gorm-hibernate5 to grails-data-hibernate5
- rename repo gorm-hibernate6 to grails-data-hibernate6
- rename repo gorm-mongodb to grails-data-mongodb
- rename repo gorm-neo4j to grails-data-neo4j
- rename repo gorm-graphql to grails-data-graph
- At this time, we have not proposed renaming packages any
further. We will discuss in the future on the artifact names.
- James D is adding `release` github environments for any grails
project. We will use that environment in the future to assist in staging &
releasing builds. More to follow after testing.
- The last remaining action item preventing a milestone 2 release is the
spring security repo merge. Mattias intends to wrap this up today.
- After the security merge is done, we intend to release milestone
2. The following people voted to proceed with a M2 release prior to the
transition to the Apache artifact names: James F, James D, Paul, Scott,
Jeff, Gianluca, & Brian.
- Mattias brought an issue with the asset-pipeline & integrationTests to
our attention. Currently it can fail. He added a work around for the
spring security projects. We will address it in a later milestone release.
- James F discussed the grails-shell & grails-forge CLIs. Specifically,
how do we handle overlap and avoid confusion amongst users.
- Long term, there was agreement that we should consider enhancing
grails-forge to take a directory structure similar to the
profile skeleton
mechanism. The hope was we could adopt the profile support into
the forge
cli and retire the shell at that time. This is not a target for Grails 7.
- For Grails 7, the proposal is to create a delegating command that
switches between the forge & shell CLI. James F to work on this and we
will discuss in the future.
