Quote:
Originally Posted by atjnjk
With the current flood of feedback, maybe you could open a M3 tracker to track bugs/features and to reduce repetition.
|
There's no need, in my opinion, to open a specifically Marvin
3 tracker. A Marvin tracker has already existed for quite a few years now, over at GitHub:
https://github.com/kguil/Marvin-Roadmap/issues
Please feel free to contribute there. There are hundreds of issues or feature requests recorded there, awaiting their resolution. GitHub is very good for tracking and eliminating duplicate requests. I find that most of the things I find missing or not working optimally in Marvin are missing or not working optimally both in Marvin 2 and Marvin 3, so GitHub is a very useful tool to keep track of them.
Of course, now with the Marvin 3 release, there will be quite a few new issues to record there, related to newly added features, and doubtlessly quite a few feature requests from the past have now been disposed of in Marvin 3.