Hi all,
OUr LEMDO project got bitten by an unexpected change in the latest TEI
release: we have a customization which deletes the Schematron rule which
disallows nested ab elements, because we believe they should be
nestable. However, the @ident of that rule was changed in the release,
so suddenly our customization failed and a pile of files were suddenly
invalid. No problem to figure out and fix, but it does show that
changing an @ident should be subject to deprecation warnings if we aim
not to catch people out with a release. I don't know how that could be
done, though.
We noticed a bunch of other unexpected changes too, and I was a bit
surprised because I subscribe to the bleeding-edge Oxygen plugin so that
I get plenty of warning of changes landing in the dev branches. However,
I think what has been happening is that a lot of changes have been
taking place in feature branches, and then languishing there until the
last-minute mad scramble to land them in dev and release branches before
the release date. That means that the value of the bleeding-edge plugin
as an advance testing mechanism is diminished. Again, not sure what
could be done about that.
Cheers,
Martin
--
------------------------------------------
Martin Holmes
UVic Humanities Computing and Media Centre
I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional
territory the university stands and the Songhees, Esquimalt and WSÁNEĆ
peoples whose historical relationships with the land continue to this day.
