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.6 Alpha. PRs to be merged and issues to be fixed. #6505

Closed
56 of 74 tasks
Jojo-Schmitz opened this issue Aug 27, 2020 · 14 comments
Closed
56 of 74 tasks

MuseScore 3.6 Alpha. PRs to be merged and issues to be fixed. #6505

Jojo-Schmitz opened this issue Aug 27, 2020 · 14 comments

Comments

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Aug 27, 2020

See also https://github.com/musescore/MuseScore/milestone/15 ;-)

PRs available:

(Copied across from #6355)

3.5 Regressions with no PR yet:

Other urgent issues with not PR yet:

  • Fix #275837: MuseScore crashes during start-up while displaying "Start center" (probably related to the below issues, at least partly, like triggered by those)
  • Fix #310942: Freezes when clicking "Copyright and download settings" in Save Online dialog (probably a musescore.com issue)
  • Fix #311727: Can't save a score online, brings up empty dialog (connected to the above issue)

Other long-time and frequent issues (where the real cause still is very unclear):

@Harmoniker1
Copy link
Contributor

Harmoniker1 commented Sep 14, 2020

@njvdberg
Copy link
Contributor

njvdberg commented Sep 15, 2020

  • #6479 - Automatic score ordering and bracketing
  • #6538 - Algorithm for spreading staves/systems over a page

@cbjeukendrup
Copy link
Contributor

cbjeukendrup commented Oct 2, 2020

@MarcSabatella
Copy link
Contributor

Thanks for staying on top of this, @Jojo-Schmitz ! A couple of notes:

  • I don't think https://musescore.org/en/node/308925 is actually a recent regression; I think the OP was confused when they reported it worked in 3.4. As far as I know, velocity has been irrelevant for SND instruments ever since SND became a thing. @jthistle can perhaps clarify

  • All the issues involving rest position are related, and to some extent are the expected results of changing layout in ways that makes some cases better, others worse. Probably these cases need to be addressed one by one. While the regression in unfortunate, 3.6 does seem like a good time to look again.

  • The two line issues are also related, connected to the new line dragging functionality, and should also be addressed together.

@Harmoniker1
Copy link
Contributor

Harmoniker1 commented Oct 23, 2020

@mirabilos
Copy link
Contributor

mirabilos commented Oct 25, 2020

This was originally part of #6742 but I split it off because ① #6759 corresponds to MU4 #6748 (which was merged into master todat) and ② #6742 now mostly deals with JSON/SMuFL topics only, for better separation of concerns, and because #6759 can basically be merged as-is.

@jeetee
Copy link
Contributor

jeetee commented Nov 4, 2020

@psmokotnin
Copy link
Contributor

Please change #6809 with #6815

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 5, 2020

done (and ticked)

@lvinken
Copy link
Contributor

lvinken commented Nov 7, 2020

  • #6834 correct MusicXML import of changed transpositions

@lvinken
Copy link
Contributor

lvinken commented Nov 15, 2020

  • 6869 fix #312714: [Musicxml Export] - Hairpin export stops halfway

@vpereverzev
Copy link
Member

No more merges for 3.6 alpha, remaining PRs (basicly WIP) will be merged in 3.6 beta)

@Jojo-Schmitz TY very much for this accounting of pull requests, it helps a lot

@Jojo-Schmitz
Copy link
Contributor Author

Should we rename this issue to "MuseScore 3.6 Alpha". PRs to be merged and issues to be fixed.", close it and start a new for Beta/Release?

@vpereverzev
Copy link
Member

Yes, it makes sense

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

10 participants