Regarding Github development triage
Because playback is import to me I can't imagine doing any serious work in MuseScore Studio until it supports
LEN and note Velocity properties as well as MuseScore 3 does. That is, Velocities working with MuseSounds and other VSTs and LEN properties function with MSBasic, MuseSounds and other VSTs.
So I'm quite curious. What does it mean when a regression is added to the 4.x SHORTLIST?
The LEN property issue is tagged Priority 2 in the SHORTLIST... but it's not currently part of the 4.4 Project.
I'm wondering if the SHORTLIST is lower priority than the 4.4 Project. Anyone know?
scorster
UPDATE 2024-06-11 = = = = = = = = = = = = = = = =
The LEN property issue is now in Github's MuseScore Studio Backlog
I'm interested to know if that means it's been promoted or demoted in priority.
scorster
Comments
+1!
616 issues to do,
31 in pogress,
69 done
In reply to +1! 616 issues to do, 31 in… by elsewhere
Yes. 616 issues brings a whole new meaning to "short list" ...
I found this Github page, where the purpose of the 4.x SHORTLIST is described as:
" ... where we keep issues we feel should be tackled sooner than those in the MU4.x project."
The SHORTLIST was updated 14 hours ago ... but I'm not sure of the accuracy of the description quoted above. Many MS 4.3 projects were completed while hundreds in the area [4.x SHORTLIST] have languished.(https://github.com/musescore/MuseScore/projects/48)
Think of the shortlist (now the backlog) as a list of WONTFIX issues.