Re: “Confirm with SB that https://github.com/TEIC/TEI/pull/2204 is ready to merge.” — agenda from yesterday’s meeting
I think I have addressed Magdalena’s (reasonable) question on the PR<https://github.com/TEIC/TEI/pull/2204#pullrequestreview-929550387>. Thus, unless she or someone else disagrees, yes, PR #2204 is, IMHO, ready to merge.
And I have just merged dev branch into the issue branch (sydb_issue-2185_URI_spaces).
Hi all,
I'd like to draw Council's attention to these two tickets:
<https://github.com/TEIC/oxygen-tei/issues/54>
<https://github.com/TEIC/TEI/issues/2251>
where two things have happened:
1. As usual, we were caught unawares when Oxygen released an update
which broke functionality in the TEI Oxygen plugin version that we
maintain. Oxygen maintain their own fork of the plugin repo and up to
now, they've been making any necessary changes silently before an Oxygen
release; then we realize that something is broken and struggle to catch
up. I now have a pull request that I've asked Radu Coravu from Oxygen to
review before I merge it, updating the included libs for transformations
to take account of log4j changes.
For those new to the situation, it's a bit complicated: the Oxygen folks
only care about ensuring that the version of the plugin that ships with
Oxygen works with the Oxygen version it ships with. However, we have
different requirements, because we attempt to maintain support for older
versions of Oxygen, so that those who cannot upgrade for some reason are
still able to get up-to-date versions of P5, the Stylesheets, and the
transformations in their older Oxygen.
This means that we can't simply adopt any of the changes that the Oxygen
folks make directly into our own branch; that would remove functionality
for earlier Oxygen versions. So we have to try to merge the changes
carefully.
When the pull request is checked and merged, then our bleeding-edge
version of the plugin will build, and those of us using it (which I hope
is a reasonable subset of the Council) are able to test and make sure
nothing is badly broken. We don't have a formal testing procedure,
though, especially for older versions of Oxygen, because few of us run
older versions.
If the bleeding edge version is deemed OK, then Council will need to
release the corresponding stable version using the procedure that's
normally followed when we do a P5/Stylesheets release.
There is a degree of urgency here because currently, anyone who is
subscribed to our plugin and has upgraded their Oxygen to the current
version will not be able to use any of the transformations, as Laurent
discovered.
2. Radu has kindly agreed to raise issues on our plugin repo when they
make changes in future, so we can try to avoid this happening again. I
think I'm the only one who watches this repo at the moment, which is not
really ideal.
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.
