User:Victor Grousset - tuxayo/Bugzilla vs GitLab

I'm trying to list big things: that is, that enough frustrating now with Bugzilla or that will be frustrating if we move to GitLab.

The main thing is replicating the signoff/qa workflow in gitlab. That is the thing that will stop any move. If we can find a way to have everything needing a signoff and a qa approval before it can be merged, then gitlab would be great --Chris 18:43, 17 August 2018 (EDT)

Pros for GitLab (libre version)

• merge requests
• free QA using the continuous integration that would automatically run against every new patch (merge request), or at least the QA tools
• editing comments
• better review UI
• trivial patches doable in the web UI
• tells if the merge request non longer applies
• upvoting comments
• the UI for upvoting issues is clear which will make this feature used way more
• being able to easily unsubscribe from the notifications of a bug without notifying everyone else (so we spam the others when muting the notifications ^^")
  • Bugzilla way: preferences → "Ignore Bugs" input
• big patches that doesn't timeout the webserver

Pros for Bugzilla

• Dependencies between bugs
• GitLab has an open core business model which makes them restrict the libre version
  • Still not much restricted. So it still have a feature set that outranks or matches more or less every other forges
• Dependency graph

Ressources

Gnome did the same switch

https://mail.gnome.org/archives/desktop-devel-list/2017-May/msg00051.html

https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure/

https://www.reddit.com/r/linux/comments/6bidyx/gnome_to_switch_to_gitlab_after_evaluating_gitlab/