We are completing a few final steps under the Grails GitHub organization and 
then will submit a ticket with ASF infrastructure to migrate the repositories 
in a few days.  It will be some number of days after that the repositories will 
migrate to the Apache GitHub organization.  

GitHub and https://gitbox.apache.org/ are synced and once moves, we will still 
work on GitHub primarily.  

On 2025/03/07 01:05:36 Michael Yan wrote:
> When will the Grails Repositories be migrated to Apache GitHub Organizaton?
> Whether they will sync to Apache GitBox?
> I'm still getting familiar with the development process for the Apache way,
> do I have to use JIRA to submit the issue first?
> 
> James Fredley <jamesfred...@apache.org> 于2025年3月7日周五 02:29写道:
> 
> > https://github.com/grails/github-actions redirects to
> > https://github.com/grails/grails-github-actions.  We will see if the
> > following workflows work or require updates.
> >
> >
> > https://github.com/search?q=org%3Agrails+grails%2Fgithub-actions%2F&type=code
> >
> >
> >
> > On 2025/03/06 18:25:53 James Fredley wrote:
> > > The following changes have been completed:
> > >
> > > Renaming GitHub Repository ✅
> > >
> > > If the repository does not start with grails- we need to rename it.  ✅
> > >
> > > rename gorm implementations (repos) to have ‘grails-data-’ prefix: ✅
> > > rename repo gorm-hibernate5 to grails-data-hibernate5 ✅
> > > rename repo gorm-mongodb to grails-data-mongodb ✅
> > > rename repo gorm-hibernate6 to grails-data-hibernate6
> > > rename repo gorm-neo4j to grails-data-neo4j ✅
> > > rename repo gorm-graphql to grails-data-graphql ✅
> > >
> > > Rename others: ✅
> > > geb to grails-geb  ✅
> > > elasticsearch-grails-plugin to grails-elasticsearch ✅
> > > github-actions to grails-github-actions  ✅
> > > grails-spring-security-core to grails-spring-security ✅
> > > grails-boot to grails-spring-boot-gsp ✅
> > >
> > > There are a few remaining repositories that have not been renamed, but
> > those are being consolidated into other repositories instead.
> > >
> >
> 

Reply via email to