Does version 3.7 development include bugs reported in v3.6.2 ?

• Jun 28, 2023 - 02:34

Sorry if this question has been covered already. For bugs reported for 3.6.2 but never resolved - Is the intention that they will eventually be fixed in 3.7 ? Or should they be re-submitted to github.com/Jojo-Schmitz/MuseScore/issues ?
I am particularly interested in github.com/musescore/MuseScore/issues/15090 (Chords over triplets disappear when time signature is changed or measures joined). This was just fixed in v4.1 Beta, but I can't move to 4 until plugins are fully supported (I realize that 3.7 has a plugin bug, but at least I can move scores back & forth between 3.7 and 3.62) .

Comments

• Jun 28, 2023 - 07:29

I am backporting 4.x fixed to 3.7 when I notice them or get notified about them (best submit an issue in my GitHub fork) and they are not too complex.
Will look into this one later, in order for me not to forget about it, better submit an issue

Reply

• Aug 8, 2023 - 23:33

Don't mean to be a pest, but I'm trying to see if I can help with 3.7 (and possibly 4.x), but I can't get them to compile. I'm on Linux Mint 20.3, I have a VM with 21.2, and another for plain Debian 12.

Am I even supposed to compile changes on my own system, or is there a magic button on Github? ;)

Any links or suggestions would help greatly. And I can't promise anything--I'm a "veteran" programmer but mostly business stuff.

Reply

Do you still have an unanswered question? Please log in first to post your question.