Jerud I think it was kind of a chicken and egg problem because it was a fundamentally new organization paradigm. People weren’t ready to change their whole system around an incomplete/buggy feature until it was “ready” so it didn’t get a ton of testing because people were only experimenting with it. Or some (like andrew) just started using mirrors recently.
Additionally the Slack was not as active or diverse as this forum, so there just weren’t that many eyes on it.
Since the Legend launch I’ve now built up a big suite of automated tests and am doing more test driven development, and now as I fix issues I’m adding tests to make sure they don’t come back. So future feature development should be a lot more stable.
But for that chicken and egg problem, maybe we should have two phases of major new feature testing, alpha and beta? So when it’s alpha, it’s something to experiment with but not necessarily ready to really use, and once it’s beta it should be considered safe enough for everyone to use? And that way in the beta phase we’d find more in depth bugs?
Also FYI, these issues have been on my mind too and I’ve been building up a test suite for them. I’m planning to jump into it and try to fix all the mirroring issues this week.