Quote:
Originally Posted by Faterson
Please reconsider, Kris. There are many things just as relevant for Marvin 2 and Marvin 3, because they are unresolved in both. What are we supposed to do then – manually copy/re-post all the issues from the Marvin 2 GitHub to the Marvin 3 GitHub?  That's going to be one hell of a chore. And, there are very instructive discussions pertaining to those unresolved issues in the current GitHub. |
Marvin 3 was written from scratch. It might as well be a whole new app.
Even if the effects of an issue are the same the technical details probably aren't.
And this gives kguil a chance to clear the air. I am sure many things
aren't relevant to both, so why mix the two together?
If a bug applies to the brand-new codebase as well, then yes, re-post that issue in the new tracker. Plus it shows you still care.
If there is relevant discussion in the Marvin 2 tracker, you can copy that too, or link to it.