Generally speaking, we don't release bug fix updates as often as some projects do, and I get the sense that a big reason for this is how much work is involved in actually producing packages for release. On the assumption that this is in fact the case, I'm wondering, what can we do to lessen / share this load?
I ask because, as is often the case with a relatively big release, there are a small number of very unfortunate regressions in 2.1 that are being reported over and over, and I would like to be able to address them. I believe we understand these issues well enough to be able to fix them quickly, and as far as I am concerned doing this is worth a certain amount of pain on our part. I think as the user base of MuseScore grows and the applications continues to be taken more seriously, we need to be increasingly conscious of how responsive we are. I think we probably all have a sense of what I am talking about, but specifically, I have in mind: - tenor drum silent due to mix up between soundfont and instruments.xml - loud pops in some sounds due apparently to a fix for a different issue - inability to enter rests by mouse on drum staves - corruption on copy/paste (or save/load) of any non-reduced tuplet - loss of information on "regroup rhythms" (at least, we should preserve enharmonic spelling) - maybe add a note to the save online dialog mentioning the dependency on LAME for custom audio? I realize that currently, producing a new release basically comes down to lasconic doing a whole ton of work mostly on his own, and I greatly appreciate all he has been doing keeping things running as smoothly as they have been. But I think it is high time we look at improving this situation. I'm not saying we should spend a lot of time putting out new releases every month or whatever, but I do think we need to have a better strategy than we do right now. -- View this message in context: http://dev-list.musescore.org/Releases-and-packaging-tp7580247.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
