Hi Leon, I didn't assume anything for the pull parser. So it's open.
I gather that you are willing to have more tests on the pull parser, so yes we could put it in the 2.0.2 branch and enable it by default if you think it's best way to go. Nicolas 2015-05-28 21:17 GMT+02:00 Leon Vinken <[email protected]>: > Just checking, "bug fixes only in 2.0.x" seems to imply we will keep using > the MusicXML DOM parser in 2.0.x and switch to the pull parser in 2.1. > Correct ? > > Note that I am not too happy about that, as it implies double work > (especially for me) on fixing MusicMXL import issues for quite some time. > On > the other hand, it does not seem like the pull parser has had a lot of test > coverage yet and when we switch I would like to have a testing period of at > least one to two months where all the nightlies use the pull parser. If we > would want to switch for 2.0.2, I think now would the time to do it. > > Regards, Leon. > > > > > -- > View this message in context: > http://dev-list.musescore.org/Preparing-MuseScore-2-0-2-tp7579373p7579429.html > Sent from the MuseScore Developer mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Mscore-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mscore-developer >
------------------------------------------------------------------------------
_______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
