Preparing MuseScore 2.1 release
The next version of MuseScore will be MuseScore 2.1. It will come with many bug fixes and some new features and will be compatible both ways with the 2.X serie. The release note is a work in progress but you can have a glimpse here
To release MuseScore 2.1 as soon as possible, we need your help. How? Read along.
Translating MuseScore
For MuseScore 2.1, we changed some sentences and added about 300 new strings. If you can read this post but English is not your native tongue, you can help. Join hundreds of translators to make MuseScore perfect in your own language!
You can find all the instructions on this page. While you are translating, you can test your changes directly in a MuseScore nightly in Help > Resource Manager. Note that you can translate the software itself, but also the video tutorials or the “Getting Started” score. Feel free to ask any questions about the translation process on the translation forum
Test a development version
Every time a developer makes a change to MuseScore, our continuous build system system creates an install package for Windows, MacOS and Linux. Anyone can then join the testing party. You just need to download a recent nightly build and try it to create or edit a score. Make sure to download a 2.1 nightly and not a master one. For MuseScore 2.1, the nightlies should be able to open MuseScore 2.0.3 files and MuseScore 2.0.3 should be able to open files created with a MuseScore 2.1 nightly.
If you find something odd, or a crash, note down the exact steps to reproduce the problem and go to Help > Report a bug. In the form, write down the exact steps to reproduce the problem. Find more instruction about how to write a good bug report
Comments
Thanks for the notice, I will install a nightly build and start using it.
Meanwhile, would it be useful to have some crowd-sourcing of the release notes themselves? I guess you've got a log of what changes were made, and that translates into a list of commits with linked issue reports, but it seems to me it could be useful to have people go through and figure out what documentation changes this entails, also to create a higher-level summary of changes, etc.
In reply to Thanks for the notice, I will by Marc Sabatella
What more could be done towards that end besides this very announcement, which links to https://musescore.org/en/developers-handbook/release-notes/release-note…?
In reply to What more could be done by Isaac Weiss
A whole lot.of those issues have no implications for documentation; they are just bug fixes. Others require updating the Handbook or other documentation. Some may require updating screenshots, some just text. And in any case, a user wondering what's new in 2.1 is going to want to see something other than just a list of issue numbers and cryptic one-line descriptions. Just seems to me it might be nice to do a prepass through the list to sort that out.
In reply to A whole lot.of those issues by Marc Sabatella
Isn't that the difference between release notes and a What's new document? The latter is not yet written...
In reply to Isn't that the difference by Jojo-Schmitz
Such as https://musescore.org/en/node/104676 and https://musescore.org/developers-handbook/release-notes/release-notes-m….
But I actually have made a couple of passes through the release notes to rewrite some of the vaguer commit messages to explain better what's changed.
In reply to Isn't that the difference by Jojo-Schmitz
Well, sure, the user-visible part of what I described is a "what's new" document. But it still seems to me a prepass through the listing in the issue tracker to identify which issues need writing up - both for that purpose *and* for documentation - makes sense. Not sure how I could explain this better. How about by example?
Given the current list of issues, we decide to start updating documentation. Someone decides they want to update, say, the Playback section of the Handbook, to make all relevant changes. So they go through each issue one by one to find all issues relating to playback, then make the changes. Someone else wants to update the section on, say, slurs. So they also go through the issues one at a time looking for issues relating to slurs, then make the changes. Someone else wants to update the text section. So they go through each issue one by one looking for relevant issues. And so on. Doesn't this seem like a lot of duplicated effort that could be reduced with a better plan?
Clarifying log messages is a start, but I'm talking about doing a bit more organizing than that.
In reply to Well, sure, the user-visible by Marc Sabatella
To me, that sounds like a description of crowd-sourcing work. But it also sounds simple enough that I'd say just do it, rather than spending the time to corall people and assign tasks.
Will it have the smart layout as advertised in developing MuseScore 3? What other new features would it have exactly? Will the PDF Converter be available there?
In reply to Will it have the smart layout by Elwin
No smart layout, no PFD convert assistant. Check the release notes.
https://musescore.org/en/download#Nightly-versions
No nightlies here for 2.1, just master ones (3.0).
no separate lists for 3.0 and 2.1
In reply to https://musescore.org/en/down by Ziya Mete Demircan
There haven't been commts to 2.1 recently.
And the mechanism that cleans up to prevent from over-using our quota and so keeps only the last X files (X apparently being 9?) seems to not look at master and 2.1 separatly.
The info that David Bolten maintains these is wrong since several years now.
There are more nightlies for Mac.
Any news to Musescore 2.1?
In reply to Any news to Musescore 2.1? by drowo
It's slowly getting there. You can follow the development here https://musescore.org/en/developers-handbook/musescore-2.1-hit-list and testing nightlies https://musescore.org/en/download#Nightly-versions
Wow, sounds great. The hit list ist is not the full "to be" release note, right? I saw a draft release note for 2.1, which looks quite impressive. I'm really exited about this new version. Thanks!
In reply to Wow, sounds great. The hit by drowo
The hit list is more a todo list, the draft release notes is a done list ;-)
In reply to The hit list is more a todo by Jojo-Schmitz
I love the done list ;-)
In reply to I love the done list ;-) by drowo
The release notes link is broken, is it not? ("glimpse here")
In reply to The release notes link is by RobFog
see https://musescore.org/en/node/152126
In reply to see by Jojo-Schmitz
Yes, thanks, I know where to find it. ;-)
In reply to Yes, thanks, I know where to by RobFog
Well, this is not good. Somehow it was moved from https://musescore.org/en/developers-handbook/release-notes/release-note… to https://musescore.org/en/administrative-guidelines/release-notes-musesc…, and I can't move it back.
In reply to Well, this is not good. by Isaac Weiss
I noticed this odd parenting when I was editing it yesterday. I didn't knowing do anything to cause it, but I did notice at once point an edit I made disappeared, which I didn't understand. Maybe someone else was trying to edit at the same time and something went wrong (normally the system prevents this)?