I generally agree with merging repositories. However, looking at grails-data-mapping, that project alone takes over 22 minutes to build in CI right now: https://github.com/apache/grails-data-mapping/actions/runs/13873050433
Den tors 3 apr. 2025 kl 14:45 skrev Søren Berg Glasius <soe...@glasius.dk>: > I agree that we should do the bigger merge. Bringing release time down > would help the project, although I know that Gradle build times will > suffer. > > Den tors. 3. apr. 2025 kl. 14.33 skrev David Estes <davydot...@gmail.com>: > > > I agree +1 we should do this! > > > > > On Apr 2, 2025, at 11:51 PM, James Daugherty < > jdaughe...@jdresources.net.INVALID> > > wrote: > > > > > > With the group / artifact name changes, we can certainly do that. I > > would > > > only want to merge what's considered a "core" release. Spring security > > for > > > example should continue to be released separately. > > > > > > That would include the following: > > > * Grails-cache > > > * grails-data-mapping > > > * grails-views > > > * grails-geb > > > * grails-gradle-plugin > > > > > > If we did this, release processes would be simple and we could iterate > > > faster. > > > > > > What are other people's thoughts? > > > > > > Regards, > > > James > > > > > > On Wed, Apr 2, 2025 at 8:52 PM Michael Yan <rainbo...@apache.org> > wrote: > > > > > >> If merging repositories has so many benefits for releases, why not > merge > > >> them all together? > > >> > > >> On 2025/04/02 17:35:28 James Daugherty 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 > > >>> > > >> > > > > > > -- > > Med venlig hilsen, > Søren Berg Glasius > > Hedevej 1, Gl. Rye, 8680 Ry > Mobile: +45 40 44 91 88 > --- Press ESC once to quit - twice to save the changes. >
