FYI, I have sent the question to Roman to check if EE would be interested in opening controlled ESDR3 Issue Register on Github (easy to do) or Jira (more complex).
Advantage are undoubted (same as what we commonly do when progressing projects at work):
- understand what test are still uncompleted
- make sure tests are not overlapping (unless directly asked)
- detailing/expanding tests if needed
- perform targeted tests (when request came from Dev)
- controlled and structured
I imagine that as a commercial company, EE will already be using JIRA or something very similar. However, I think that exposing/sharing JIRA (or for argument's sake, anything similar) to a paying customer as part of a project (under contract), is somewhat different to putting that sort of information in to the public domain, where it is easily accessible and open to analysis by competitors.
I certainly think you're right that some visibility of logged issues would help (it would reduce multiple bug reports being raised for the same issue). When it comes to testing, maybe an army of NDA'd beta testers would work...from my observation of Elecraft years ago, that worked very well.
My own reflection is that the dev/test/release/bugfix cycle for Vers 3 as it rolls out and matures/grows will be quite different to that experienced by EE on the slower burn of Vers 2. Maybe the best we can do as 'punters' at the moment is just to let EE know that there are individuals here that can assist if they want..