>> Agreed. What you're refering to is, I believe, usually called "Migration >> guide". Maybe a wiki page on github would be good? > > I think that'd be a great way to do it.
Ok > Both models (and probably many others) are equally valid, so the > decision is really based on your concerns. If you think the master > should be the bleeding edge in order to keep things easy and encourage > contribution, using Br. Samuel's suggestion, then I would additionally > suggest the use of a "stable" tag on the current stable version, so that > someone checking out the git repository doesn't have to actually inspect > the repository to "git checkout" the stable branch. I believe having master as "stable" branch seems the best idea. > Have two repositories (not branches): gregorio and gregorio-beta. I admit I'm not really inspired by this, I really don't see the benefit, and I clearly see the disadvantage of having multiple repositories (more complex to handle)... But if everyone agrees on this, why not. > The obviously easiest things to find would be compile problems. As for > comparing output, the PDFs cannot be compared directly because of the > creation date and modification date values embedded within the PDF > itself. I was thinking of using imagemagick to compare, but I still > have to work that out. Indeed, seems like a good idea, but there are always cases where these tests won't work (a slight change in the spacing algorithm, a change of shape of one glyph, etc.). Or maybe the best approach would be to have different test methods, and to decide, test by test, which to use. There could be - gabc->gregoriotex tests, testing the .tex output for some specific mechanisms - gabc->dump tests, comparing the dump output for the internal structure, mainly for gabc syntax tests (for pure gabc, these would be more accurate than the first ones, as the "dump" output almost never changes, so tests will be more relevant) - some gabc->gabc tests, to see if some structures are recognized (not sure how relevant this would be) - score inclusion and compilation tests, testing the presence of files - tex tests testing some annotations, initials, etc. comparing output with imagemagick - etc. Thank you, -- Elie _______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
