Preparing MuseScore 3.0 Beta release
Next public version of MuseScore 3.0 will be MuseScore 3.0 Beta. It comes with a lot of fixes made after Alpha 2 release.
Translating MuseScore
We are going to push new strings from MuseScore 3.0 to Transifex. It means there will be a lot of new strings to translate. We need your help to finish translations.
You can find all the instructions on this page. While you are translating, you can test your changes directly in a MuseScore nightly in Help > Resource Manager. Feel free to ask any questions about the translation process on the translation forum.
Attention!
Last stable version MuseScore 2.3.2 won't get updates for translation anymore. All translations will be applied to MuseScore 3.0 only.
Test nightly version
Every time a developer makes a change to MuseScore, our continuous build system creates an install package for Windows, macOS, and Linux. Anyone can then join the testing party! You just need to download a recent nightly build and try it to create or edit a score. MuseScore 3.0 nightly builds are able to open both 2.X and 3.0 files.
If you find something odd, or a crash, note down the exact steps to reproduce the problem and go to Help > Report a bug or find and click a Bug icon in toolbars. In the form, write down the exact steps to reproduce the problem. Find more instruction about how to write a good bug report.
Feel free to start using new testing facility we implemented to cover user scenarios with easy to create, easy to use testing framework.
MuseScore 1.X scores compatibility
Files created in earlier versions of MuseScore should be opened, but we don't guarantee any changes will work correctly. It is recommended to open the old score in MuseScore 2.3.2, save and open in MuseScore 3.0 after that.
What should be done
Recently we changed issue tracker categories semantic. Priority field is used to highlight the most important issues which should be addressed in upcoming release, so that the issues with P0-Critical priority becomes the most important bugs to fix.
Comments
This is exciting! A couple of questions you may or may not be ready to answer but deserve discussion:
1) the obvious one - any target date for this? or is it a matter of resolving all P0 bugs?
2) will "beta" more or less correspond to "feature freeze"?
3) will MuseScore 3 Beta be supported on musescore.com?
In reply to This is exciting! A couple… by Marc Sabatella
1) November, all P0 issues should ideally be fixed
2) feature freeze already happened. Mixer was the last big change.
3) Will see, I don't have definite answer here.
In reply to 1) November, all P0 issues… by Anatoly-os
Thanks! I guess a followup to question about feature freeze would be to think about string freeze and GUI freeze, as these are relevant to translators and documentation. Not that I'm advocating for strictly-enforced hard freezes, but to get some sense of when it's OK to really begin translation or documentation in earnest without too much risk of further changes. I guess the answer is probably that we are more or less at that point already as well?
In reply to Thanks! I guess a followup… by Marc Sabatella
Translations just started, but right now it is too early for a string freeze. That can happen after beta, shortly before an RC
In reply to Thanks! I guess a followup… by Marc Sabatella
Congratulations on the progress folks...