If you follow this list, you know that we started a thread about migrating git.centos.org (pagure) to gitlab.com/CentOS
We are now to a point where we can easily migrate everything, and have a parallel server hosting the tarballs/sources (aka lookaside cache server)
I'd like to target second half of August for real migration and so shutting down git.centos.org (basically when I'll come back from summer holidays)
While already migrated projects are already aware of it (and reflected new url in their workflow), I'd just like to ensure that SIGs still relying on git.centos.org for rpm packaging *should* migrate this before the migration.
Reminder : all /rpms/* projects hosted on git.centos.org will be (already mirrored) just available on https://gitlab.com/CentOS/archives/git.centos.org/rpms/ , but with the archived bit turned on, so without any way to open MR or push directly to any branch. Current situation was that based on SIG membership/group, people could push to specific branches on projects under /rpms/* So be sure to create yourself new projects under your SIG group (if you don't have one -yet- , create an infra ticket to ask for one) under https://gitlab.com/CentOS/ and migrate what you need to your own projects (see for example Hyperscale, Virt, Storage SIGs, etc , already using gitlab)
I'd don't have a list of all SIGs still using git.centos.org but as one example, I know that Cloud SIG (for openstack) was still using it and I don't see any rpms under https://gitlab.com/CentOS/cloud/rpms ..
So be ready before the real migration and so before we'll shutdown git.centos.org
PS : of course we'll just migrate everything to gitlab, so you can still pull/clone from there and then push to your own new project there, and we'll also keep full backup of git.centos.org (pagure) so nothing will be lost