On Tue, May 16, 2017 at 11:15:51PM +0900, Tristan Van Berkom wrote: > I don't share your optimism about gitlab bug tracking, nor do I share > in the mentioned frustration with bugzilla.
Me too, I like bugzilla (but not for doing code reviews). What would be the pain points if GitLab is used only for git and code reviews, and we keep bugzilla for the bug tracker? Have you considered that option? We would loose automatic links between bug tracker tickets and pull requests. When a pull request is merged, we would need to close manually the bugzilla ticket if everything is done. And when someone requests a pull, the person would need to add a comment manually on bugzilla so that other people know that the bug is being worked on. Mmh I think that's not practical if the links must be done manually. Maintaining the bugzilla instance would also require sysadmin time, and development efforts to rebase the patches to new bugzilla versions. I don't know, I'm excited about the idea to use a similar contribution workflow as in GitHub, but less excited about having a bug tracker similar to the GitHub one. (I've never used GitLab, but I'm familiar with GitHub, and after seeing some screenshots it seems that the GitLab bug tracker is similar to GitHub's). -- Sébastien _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list