Am 17.09.2018 um 17:12 schrieb doctormo@...400...:

Dear developers,

One of the discussions we had in Kiel was the potential to host a
tracker to document some of the regressions that we have on GitLab.
While we're keeping the inkscape issues tracker closed for now, I've
created a project to hold the regressions for 1.0. These are mostly for
programmers to document errors and talk between ourselves about
possible solutions, rather than end user issues.

https://gitlab.com/inkscape/regressions

I don't think this'll interfere with anything, but let me know if it
opens too many problems and I'll close it down.

Best Regards, Martin Owens

Hi Martin,

personally I'm afraid it will make it even harder to keep track of issues, as it will be a separate/parallel location to report issues next to Launchpad, so we'll have all the problems of separate trackers (most importantly duplication and twice the effort for a single search) with no real gain (at least I did not hear any real arguments for this solution except developers being to "lazy" to search for new regressions in the existing bug tracker, which is a non-issue though, see below).

Two additional things to remember:

• There's no good way to move individual issues from Launchpad to GitLab, so if our users report a regression on Launchpad it will involve manual effort to move it (or cause duplication) and it will detach the original author from the issue on GitLab.
• Once we're ready to move away from Launchpad we'll be in a situation where we have not only one but *two* trackers that we need to somehow consolidate into whatever our future bug tracking will be.
  

I'd prefer if we just used the already existing "regressions" tag on Launchpad [1]. If we want to fully separate older regressions from new ones we can use a suitable milestone or an additional tag like "1.0".

Best Regards,
Patrick


[1] https://bugs.launchpad.net/inkscape/+bugs?field.tag=regression