On Fri, 10 Jun 2016, Jonathan Dowland wrote: > I was wondering what the Gitlab proponent's thoughts are on how the Issue > tracker functionality of Gitlab should be used in a Debian context, > particularly in how it might intersect/interact/conflict with the BTS.
You can enable/disable it per project, might be a good idea to leave it enabled for upstream projects, and leave it disabled for debian package projects. Also, you can use external "issue trackers" in gitlab, and these are also per-project. It has special support for Redmine and Jira (one for the Debian BTS would have to be written). It has very limited support for an email workflow in its native issue tracker. I didn't check how well the native gitlab issue tracker would play with the Debian BTS upstream forwarding. But it is way more limited/simpler than the Debian BTS. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
