+1 Gianluca Sartori -- Cell. +39 388 1026822
On Wed, 2 Apr 2025 at 19:38, James Daugherty <jdaughe...@jdresources.net.invalid> wrote: > Hi Everyone, > > As we discussed in last week's weekly meeting, we have a desire to merge > grails-cache into grails-core. We want to continue to merge repositories > to simplify our release strategy and reduce the time to publish artifacts > (so we can spend time on developing and not releasing). > > Recall that the current release process works like this: > 1. Pre-release grails core (publish to temporary repo) > 2. Release grails-data-mapping > 3. Pre-release grails core (publish to temporary repo) to pick up data > mapping version > 4. Release grails-views > 5. Pre-release grails-core (publish to temporary repo) to pick up > grails-views version > 6. Release grails-geb > 7. Pre-release grails-core (publish to temporary repo) to pick up > grails-geb version > 8. Release grails-cache > 9. Pre-release grails-core (publish to temporary repo) to pick up > grails-cache version > 10. Release grails-gradle-plugin > 11. Pre-release grails-core (publish to temporary repo) to pick up > grails-gradle-plugin verison > 12. Release grails-profiles > 13. Release grails-core with the included grails-profiles > > Because so many of these repositories refer to other repositories in this > list, these steps ensure the following: > > - We don't depend on a prior unreleased version > - We release all artifacts with a consistent version > - The artifacts do not depend on a snapshot version in their POM. > > Prior to the merger of repositories, there used to be 30+ of these. We are > now down to 7 repositories. This took the release time down significantly, > and it continues to decrease as we merge them. Each step above can take > 10-20 minutes as they are composed of smaller steps not mentioned here. > > Given this overview, and the benefit of simplifying our release process: is > anyone currently against merging grails-cache into grails-core? > > I'm currently in favor of this as I'd rather spend time working on Grails, > not on Grails' Build & Release processes. > > Regards, > James >