Han-Wen Nienhuys <[email protected]> writes: > On Sun, May 10, 2020 at 11:37 AM David Kastrup <[email protected]> wrote: >> >> Han-Wen Nienhuys <[email protected]> writes: >> >> > Sorry. I'm fine with the migration going through today. >> > >> > We'll all be confused for a few days, but given that gitlab is more >> > standard infrastructure than what we have, I think we'll figure it >> > out. >> > >> > I suggest: >> > >> > * removing write access to issue tracker from me, so patch upload >> > fails appropriately >> > * stopping the job that mirrors staging => master (I think it runs >> > automatically?) >> >> Semiautomatically these days. Why would that task need stopping? It >> would just need to get run with the Gitlab repository instead, or am I >> misunderstanding anything here? > > I think it would be good if nobody commits to either GL or savannah > during the migration, to not muddle the waters. Afterwards, it can > work off GL.
Sure. But as long as nobody pushes to staging, nothing will get to master anyway. I just remembered: we should not be mirroring staging since Savannah will refuse any non-ff push to any branch, and staging will be non-ff whenever something needs to get backed out of it. -- David Kastrup
