When can we expect an update to 1.x ?
Hello there,
Recently there have been a number of items in the bug tracker saying 'fixed in branch' which I take to mean fixed in the v1 development stream. How soon can there be a release of 1.x stable incorporating some of these fixes?
There doesn't seem to be much point fixing things in svn if they are not released.
Or is there a pre-release of 1.x available somewhere?
...If so where?
Nightlies all seem to be for v2
Comments
I'm currently the maintainer of the 1.x branch. There are still a couple of bugs I would like to see fixed. I would love to make a release around end of june, beginning of july, preceded by one or two prereleases, but it will depend how fast the bugs are fixed.
In reply to I'm currently the maintainer by [DELETED] 5
Thanks for the timescale lasconic. I will look forward to the release.
Thanks for all you effort, its a great programme.
In reply to Thanks for the timescale by BarrieB
cho
ho
o.
In reply to I'm currently the maintainer by [DELETED] 5
Great to hear! I mentioned this on the developer's mailing list, but I am interested in contributing a few things to this release. My jazz lead sheet and big band templates and my customchords.xml file for starters. They are almost-but not-quite ready to go; I could have them all fixed up by whenever you might need. I also I might want check in some additions to instruments.xml for the benefit of drumset parts if that were acceptable. Just let me know.
In reply to Great to hear! I mentioned by Marc Sabatella
Hi Marc,
I answered on the mailing list. Hope you get it. There is no problem to commit the chords files and the templates. Same for instruments.xml files (the translations will need a review though). Just send a zip file on the mailing list and I will review and commit, in the trunk as well.
In reply to Hi Marc, I answered on the by [DELETED] 5
Thanks for the pointer - for some reason I had missed the reply on the mailing list. I'll get on it right away.
For me, priority should be things that leave a mess (sometimes irreparably).
Other things such as #7765: Beam should reach center line for notes beyond one ledger line are lower priority, because it's not jeopardising the score itself (the coding of the version determines how that's controlled - unless manually adjusted maybe).
1) Corruption:
Mainly caused by copy and pasting (multi-voice or otherwise) or changing time signatures. Such scores may not open in future versions (crash), and it would be good to smooth these things out for better transition into the eventual 2.0 version.
http://musescore.org/en/node/9875
http://musescore.org/en/node/10793
Something like these too perhaps:
http://musescore.org/en/node/9077
http://musescore.org/en/node/9125
2) Mess that can't be undone/corrected, or where undo causes crash:
#9909: Copying single tuplet pastes as standard note and produces tied mess upon undo
#8978: Mixer excludes instruments after undoing instrument removal, with changed settings
In reply to For me, priority should be by chen lung
Another issue for 2: #9085: Undoing transpose leaves behind notes featuring ties
It's not as important as the others, but it would serve as a useful fix: #11078: Disallow part with no instrument
Another issue which could cause problems in the transition to 2.0: #10577: [Trunk] Applying arpeggio to note with tie before it causes crash
In reply to Another issue which could by chen lung
Putting the issue in the issue tracker is enough. You don't need to post it again here.
In reply to Putting the issue in the by [DELETED] 5
There's many bugs, but I'm just selecting the ones I feel need priority.