Well, this is not necessarily a bug report; take this more as a suggestion.
The problem I'm seeing is that the last releases of Sonic Visualiser came with some outstanding issues, like installation packages not installing, program crashes, some minor (or not so minor) usability issues, etc. And I see also that the main developers aren't having much time to work on SV, and I understand this perfectly (I'm not condemning you, Chris).
What I would like to suggest is to, before releasing a new version, publish a Release Candidate version, which could be tested by the community. This version could be announced on a mailing list, and by SV itself. SV could have an option in the Preferences dialog to notify the availability of beta versions (disabled by default, of course).
Despite the fact that SV as an open source project doesn't have a huge community, I'm sure that there will be some people (like me) interested in carrying on some testing when a new non-stable version arrives. And I think we and the end users can avoid some headaches if we have a pre-release version and we concentrate some testing, bug hunting and correcting in one week or two before launching a supposedly stable version.
And thank you for tolerating my bad english... :-)
Log in to post a comment.