Philip Hands <> writes:
> Gert Wollny <> writes:
> ...
>> Short version: Use the salsa per-package issue tracker for problems
>> that come up with the review in NEW.
> Is there any significant benefit that this brings over having the same
> interaction in the BTS?
> I realise that Gitlab is the new shiny thing, but there is a cost to
> using two issue tracking mechanisms when one would do, and for packages
> where the maintainer is not actually using salsa, what then?

I would rather like to see the salsa issue page to the BTS (so that "new
issue" would create a new BTS entry).



Reply via email to