On Mon, Oct 26, 2020 at 11:04:06AM +0000, Peter Maydell wrote: > On Thu, 22 Oct 2020 at 17:48, Paolo Bonzini <pbonz...@redhat.com> wrote: > > now that Gitlab is the primary CI infrastructure for QEMU, and that all > > QEMU git repositories (including mirrors) are available on Gitlab, I > > would like to propose that committers use Gitlab when merging commits to > > QEMU repositories. > > > Nothing would change for developers, who would still have access to all > > three sets of repositories (git.qemu.org, gitlab.com and github.com). > > Committers however would need to have an account on the > > https://gitlab.com/qemu-project organization with access to the > > repositories they care about. They would also lose write access to > > /srv/git on qemu.org. > > Yes, this makes sense. Who in practice does it actually affect? > For the main qemu.git repo, my guess is just me, Michael Roth > for the stable branches, plus Richard H and Stefan H who both > volunteered to do a turn on the merge-handling rota once we > eventually get it set up to not depend on my ad-hoc CI setup. > > I have a gitlab account so I'm set for this. Michael, do you > have an account there and are you OK with switching to doing > git pushes to the repo on gitlab rather than direct to qemu.org ?
That's fine by me. My gitlab account is @mdroth, and I've requested access to qemu.git and qemu-web.git subgroups. My only concern would be what the lag time might be between updates to qemu-web.git and the actual website update if the mirroring doesn't right away. Probably not a huge deal but might be good to know what the upper bound is if we want to verify the update process went okay. > > thanks > -- PMM
