Thanks James for this information, I’m a newbie regarding the way the lilypond-devel people operate.
JM > Le 3 sept. 2018 à 12:49, James Lowe <pkx1...@runbox.com> a écrit : > > Hello Jaques > > > On 02/09/18 20:33, Menu Jacques wrote: >> Hello James, >> >> >>> Please also don't forget that it (whatever 'it' is, and assuming it is >>> accepted) will need to work when run against our regression tests (i.e. >>> make test-baseline/check). >>> >>> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#musicxml-tests >>> >>> <http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#musicxml-tests> >> These tests are what I named the Unofficial Test Suite in my OP, as they >> were called when I started my project. Most of them are already translated >> satisfactorily by xml2ly. >> >> JM > Sorry, I am not a developer just the Patch Meister who currently also tests > and checks all patches via our 'make' scripts. > > So if your code was added 'now' and I were to run autoconf and then make > test-baseline/make check commands the xml2ly function would be exercised > properly (and then again for any new patches that were added) If not then the > additional code changes I was referring to would be specifically to do with > the regression test part of all our make scripts. > > James _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
