Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MuseScore 3.5 Release Candidate. PRs to be merged #6195

Closed
1 task done
anatoly-os opened this issue Jun 10, 2020 · 30 comments
Closed
1 task done

MuseScore 3.5 Release Candidate. PRs to be merged #6195

anatoly-os opened this issue Jun 10, 2020 · 30 comments

Comments

@anatoly-os
Copy link
Contributor

anatoly-os commented Jun 10, 2020

@RobFog
Copy link

RobFog commented Jun 10, 2020

#4757?

@shoogle
Copy link
Contributor

shoogle commented Jun 12, 2020

@ecstrema
Copy link
Contributor

ecstrema commented Jun 13, 2020

@Spire42
Copy link
Contributor

Spire42 commented Jun 14, 2020

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jun 16, 2020

Issues without PRs (yet):

(Issues with) PRs:

@worldwideweary
Copy link
Contributor

worldwideweary commented Jun 17, 2020

@tobik
Copy link
Contributor

tobik commented Jun 17, 2020

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jun 19, 2020

Still not totally clear on the criteria for what is being considered, but to me these are good candidates. They are not regressions (well, not new regressions in 3.5 anyhow) but they do address some real pain points that are easily solved. And they don't involve new strings or otherwise require new documentation, they just allow things to work that people have every right to expect to work anyhow.

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jun 20, 2020

The following issue needs to be resolved:

https://musescore.org/en/node/307005.

The following PR addresses it directly:

And then also

Another possible approach is #6259 which disables chord symbol playback for pre-3.5 scores, but I think the consensus is #6268 is preferable.

@tobik
Copy link
Contributor

tobik commented Jun 21, 2020

@jeetee
Copy link
Contributor

jeetee commented Jun 23, 2020

@AntonioBL
Copy link
Contributor

AntonioBL commented Jun 23, 2020

@shoogle
Copy link
Contributor

shoogle commented Jun 23, 2020

@lvinken
Copy link
Contributor

lvinken commented Jun 24, 2020

  • #6256 low risk MusicXML import/export improvements

@Spire42
Copy link
Contributor

Spire42 commented Jun 24, 2020

By popular demand. Undoes the change to the default zoom type that was made in #5623.

@rettinghaus
Copy link
Contributor

rettinghaus commented Jun 26, 2020

@lvinken
Copy link
Contributor

lvinken commented Jun 28, 2020

@MarcSabatella
Copy link
Contributor

I edited a comment above to list #6268 (changes default playback sound for chord symbols to piano) as the consensus on how to handle compatibility/surprise concerns for older scores with chord symbol playback.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jun 30, 2020

Yet unresolved issues (without PRs, as those don't make sense there):

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jul 2, 2020

@CodeforEvolution
Copy link

This would really help to have this added to the 3.5 release, as it would make it easier for the folks over at HaikuPorts (Haiku’s main package management repo).

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jul 6, 2020

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jul 7, 2020

@Harmoniker1
Copy link
Contributor

Harmoniker1 commented Jul 7, 2020

This PR also fixes an issue of the stem length becoming a bit longer than necessary for chords with tremolo strokes and a downward stem.
It also makes one-note tremolo layout slightly better.

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Jul 8, 2020

I'd like to see this PR in 3.5RC, even if not being a 3.5 regression, but it finally seems to make continuous mode with lyrics usable again:

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jul 10, 2020

No PR yet, but this is a serious regression that needs to be fixed:

@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jul 10, 2020

I believe this is important for 3.5, otherwise people will employ workarounds that will break when this does get fixed:

@anatoly-os
Copy link
Contributor Author

Congratulations with 3.5 Release Candidate! https://musescore.org/en/3.5rc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests