Preparing MuseScore 2.0.1 bug fix release

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Preparing MuseScore 2.0.1 bug fix release

lasconic
Administrator
Hi,

After the release of MuseScore 2.0 we got some expected bug reports. Marc Sabatella maintains a list hereĀ http://musescore.org/en/issue-hit-list-marc-sabatella

Let's release MuseScore 2.0.1 asap to fix the most serious bugs.

I created a 2.0 branch from the v2.0.0 tag https://github.com/musescore/MuseScore/tree/2.0 and I cherry picked the commits worth having in 2.0.1. I would propose to keep doing this. Master is dedicated to 2.1 development and we work on it. Then we backport fixes to the 2.0 branch for MuseScore 2.0.1 release. If you contribute via pull requests, you can continue to send PR to the master branch.

From now on, the nightly builds will also use the 2.0 branch so we can all test the bug fixes and have a strong 2.0.1 release.

If you have questions or remarks, feel free to pop onto our IRC channel #musescore on freenode.net

lasconic

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer