Quote:
Originally Posted by kguil
@Everyone Please note that when things settle a bit, I will be setting a new GitHub repository for tracking issues specific to M3. The current one is/was for M2 only.
|
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.