Good question, Elisa. The difficulty is that you have to have local build capability to *thoroughly* test a Stylesheets/ branch other than that which Mr. Jenkins would test. But to do *some* (perhaps a lot of) testing is really easy: check out the branch in question, then $ cd /path/to/that/branch/of/Stylesheets/bin/ $ ./teitorelaxng --odd /path/to/a/test.odd $ ./teitodtd --odd /path/to/a/test.odd # and, I suppose $ ./teitoxsd --odd /path/to/a/test.odd This puts tangled schemas into /path/to/a/test.odd.relaxng /path/to/a/test.odd.dtd /path/to/a/test.odd.xsd Then you can eyeball those schemas, load them into oXygen and validate them, and try to make test files against them. If and when you want to make the process faster, you can get yourself a local copy of TEI/P5/p5subset.xml and point to it with the --localsource switch. E.g.: $ cd /tmp/ $ wget http://www.tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.xml $ cd /path/to/that/branch/of/Stylesheets/bin/ $ ./teitorelaxng --odd --localsource=/tmp/p5subset.xml /path/to/a/test.odd The trick here is to ignore the built-in help from `teitorelaxng --help`, which says that the --localsource switch should point to a directory; it should point to a compiled copy of the P5 source. (I think I have a ticket in on that already.)
... don't we need to pull in Syd's branch, or are we testing the Stylesheets using that branch to make sure the updates work properly prior to release?