Don't prompt with new version if it's a dev version.

• Dec 31, 2018 - 18:16
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project

In MuseScore 2.3, I was prompted that there was a new version, which is apparently 3.0-dev.

However, 3.0 dev doesn't seem stable enough to use and seems to be marked as a development version rather than a final version.

MuseScore should not prompt that a new version is available if the new version is an unstable development version rather than a stable release version.


Comments

In reply to by mike320

Sounds like it was just the name of the release in the bug tracker that referred to it as a development version. But it doesn't seem stable enough for me to use. I immediately ran into quite a few problems, and they didn't seem to have workarounds. It isn't useful to me in its current state, so I've gone back to 2.3. Please see the other issues I've submitted for details.