Which issues are still considered for 3.5 ?

• Jun 21, 2020 - 20:41

Could someone explain which issues are still considered for inclusion in 3.5 ? Do we focus on stability (fix showstoppers only) or completeness (everything goes, potentially delaying the release) ? Is the strategy published somewhere ? Do we have a list of must-have issues ?

Also see discussion in https://musescore.org/en/node/306725.

Furthermore, the proposed changes for 4.0 seem quite large. This suggests one or more bug fix releases may be required between 3.5 and 4.0. Once again, what is the strategy ?


Hi Leon. I think your changes of getting an answer to your questions from the people who have a say in this are better in the developers' Telegram channel.

3.5 is hanging between beta and rc state:
Accepted fixes:
* regressions introduced since 3.4.2
* criticals
* low impact fixes

We expect to release 3.5.x versions with additional bug fixes.
There is no intention of releasing 3.6 (so no new features on 3.x)

Development of new features must all happen against master, which is undergoing the major architecture rework for MS4. Expect nearly all modules to change besides the core functionality (libmscore) and import/export modules.

The above is no official stance, but the information I have gathered over the past two weeks in the developers chat

In reply to by Leon Vinken

As far as I can tell, it's possible to view shared Web links to individual chat messages, but it isn't possible to browse chat history without getting the app and joining the group.

Even though it requires a specific app to access, it's still open to the public.

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