should go to 2.1 and master. The PR is for master, however I see no reason for it not to apply cleanly to 2.1 too
Apparently this reverts my (errnous) change from f5e1b2e6 (master) and baf84a4 (2.1), I guess I was thinking that this brings up some file selection dialog.
Version 2.1 is not really lower than 3.0 (only the number is lower), they are living in parallel universes ;-)
Hmm, if you want it in 2.1, why a PR against master?
Anyway, it's not that important against which releases it is reported, important is that we want it fixed in 2.1 and master, document that and check it happens.
I'm not going only by my own logic, either. Other bug trackers, such as LibreOffice's and Firefox's, have this clearly in their guidelines (and I'll add it to our own "How to"):
Choose the version of the application in which the bug appeared.
Comments
https://github.com/musescore/MuseScore/pull/2975
should go to 2.1 and master. The PR is for master, however I see no reason for it not to apply cleanly to 2.1 too
Apparently this reverts my (errnous) change from f5e1b2e6 (master) and baf84a4 (2.1), I guess I was thinking that this brings up some file selection dialog.
The button does not even exist in 2.0.3, however. ;-)
It does in master, and 2.0.3 is the common denominator?
I thought it was supposed to be the earliest version that the problem actually appears in.
Version 2.1 is not really lower than 3.0 (only the number is lower), they are living in parallel universes ;-)
Hmm, if you want it in 2.1, why a PR against master?
Anyway, it's not that important against which releases it is reported, important is that we want it fixed in 2.1 and master, document that and check it happens.
I'd say 2.1 is lower than 3.0, since everything in 2.1 is also in 3.0. PR against master because it does affect both.
But there's absolutely no question that this bug does not affect 2.0.3, and it should not be labeled as such. Same for #165711: Staff properties: Apply/OK does not update changes to previous staves, and I'm not sure what else.
I'm not going only by my own logic, either. Other bug trackers, such as LibreOffice's and Firefox's, have this clearly in their guidelines (and I'll add it to our own "How to"):
https://wiki.documentfoundation.org/QA/BugReport
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guideli…
Fixed in branch master, commit ac9de15554
Fix #165771: Ellipsis on "Load" button when adding SFZ in Zerberus
Fixed in branch master, commit bde7f75fa2
Merge pull request #2975 from IsaacWeiss/165771-zerberus-load
Fix #165771: Ellipsis on "Load" button when adding SFZ in Zerberus
Fixed in branch 2.1, commit f18de72640
Fix #165771: Ellipsis on "Load" button when adding SFZ in Zerberus
Automatically closed -- issue fixed for 2 weeks with no activity.