Which issues are still considered for 3.5 ?
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 ?
Comments
https://github.com/musescore/MuseScore/issues/6195
issues to be solved.
In reply to https://github.com/musescore… by Sunny2019
Further pull requests can be proposed there.
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
Thanks to all who replied. I strongly believe in having this information publicly available instead of only in the chat.
In reply to Thanks to all who replied. I… by Leon Vinken
Well, the chat is publicly available. Including all its history
In reply to Well, the chat is publicly… by Jojo-Schmitz
Where ? Does that require the app (which I don't use) ?
In reply to Where ? Does that require… 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.
In reply to Well, the chat is publicly… by Jojo-Schmitz
I do think it would make things easier for developers if project management were make the roadmap transparent. It's not reasonable to expect every developer to read the channel which has hundreds of messages daily.
In reply to Thanks to all who replied. I… by Leon Vinken
I've made an attempt at providing some information about the release process in https://musescore.org/en/handbook/developers-handbook/references/musesc…
https://musescore.org/en/node/306875
In reply to https://musescore.org/en… by mjbartemusica1
Is fixed as far as I can tell, see #306878: Plugins with dialogs open their dialog in the background (behind the main MuseScore window)
Not in the Beta, but will be in the RC
In reply to Is fixed as far as I can tell by Jojo-Schmitz
Hello Jojo!
What is the difference between Beta and RC? I don't know the meaning of both.
At least on my Windows 10 system and version 3.5 Beta and problem continues.
Hug!
In reply to Hello Jojo! What is the… by mjbartemusica1
Release Candidate. Not yet existing, but will shortly