Seems reasonable to me...in the old Subversion days, we called it 'trunk'...then 'master' with Git...but calling the main development branch 'main' is arguably the simplest and most descriptive term.
One thing we'll have to coordinate: getting Gitlab CI / Marge and the Intel Mesa CI to switch over at the right time, so we don't end up breaking/interrupting those services. Should be easy, just requires a bit of coordination. --Ken
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
