On Tue, 2017-05-16 at 14:22 +0100, Allan Day wrote: > In recent months we have got together to examine the possibilities > for GNOME’s development infrastructure. We’ve spent a lot of time on > this, because we want the community to have faith in our conclusions. > If you are interested in this, you can read our research on the wiki > [1].
I’m excited for this. I think my main concerns have already been raised by others, but I’ll raise them as a +1: - Dependencies between issues (the workaround of listing them all in a comment isn’t very satisfying, but will do in the interim if we are sure a proper solution is coming) - First-class support for a fast-forward merge workflow, including not losing comments when doing a force-push to an MR - Not breaking any old links when migrating cgit/Bugzilla bugs/Bugzilla attachments With those concerns in mind, I’m enthusiastic for gitlab. I would also be supportive of a solution using Phabricator+cgit. Phab for task management and patch review, since its task management is more powerful than gitlab’s, and its patch review workflow doesn’t have the problems of gitlab’s branch-and-merge approach (its inter-diff reviews are great). cgit for viewing the repositories, as normal. Philip
signature.asc
Description: This is a digitally signed message part
_______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
