April 2022 - Tei-council - lists.tei-c.org

Next stylesheets meeting: April 22
by BERMUDEZ SABEL Helena 22 Apr '22

22 Apr '22

Dear all, The next Stylesheets meeting will take place on April 22th at 16.00Z (8.00 PDT, 11.00 EDT, 17.00 CEST). As discussed in the VF2F meeting, we will dedicate a Stylesheets meeting to address the oXygen plugin and its maintenance, and Martin Holmes kindly accepted to walk us though the basics. This introduction will be the main point of the agenda<https://docs.google.com/document/d/1LHIhvuNTISCrlMZDZx7jkVbDt8teivQTbJrF0EV…>. See you all on Friday and good luck to the release techs today! Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel

4 4

Deprecation for ident changes?
by Martin Holmes 22 Apr '22

22 Apr '22

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.

3 4

altIdent screw up
by Bauman, Syd 21 Apr '22

21 Apr '22

Oh BLEEP! I failed to change the manual deprecation date from "2022-07-14" to "2022-10-21" on the "deprecate_altIdent_in_non-ODD_places" constraint specification (in file P5/Source/Specs/altIdent.xml). Now that we have published 4.4.0 with the “wrong” date I see 3 possible courses of action: 1. Leave things as is, and just act on the deprecation on 2022-07-14. Yes, that makes the deprecation period pretty short, but who uses `<altIdent>` anyway? 2. Do nothing in July. For the _next_ release (call it 4.5.0, as that is likely what it will be) reset the valid until date from 2022-07-14 to a date a few months after the 4.5.0 release. 3. Issue a point release (4.4.1) now that corrects the date to the desired 2022-10-21.

3 3

Freeze lifted
by Raffaele Viglianti 20 Apr '22

20 Apr '22

Dear Council, The release process is completed, feel free to start pushing to dev again! Raff

2 1

Entering Freeze period for v 4.4.0
by Raffaele Viglianti 17 Apr '22

17 Apr '22

Dear, All, I have now created the release branch for version 4.4.0 of the Guidelines (https://github.com/TEIC/TEI/tree/release-4.4.0) and for version 7.53.0 of the Stylesheets ( https://github.com/TEIC/Stylesheets/tree/release-7.53.0) Please refrain from committing anything to dev until the release is completed. If you wish to make changes to the release branches, please notify the release technicians before pushing any change. The technicians are: Janelle Jenstad, Hugh Cayless, Raff Viglianti. Could the Jenkins maintainers add these branches to be built? Thanks everyone! Raff

1 0

release notes
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 Apr '22

15 Apr '22

Dear all, I made a first draft of the release notes: https://github.com/TEIC/TEI/commit/6f9fd2aef3a1c6403843d1293499960e5d3e8be7 To be continued tomorrow. Best, Martina

1 0

how many namespaces?
by Bauman, Syd 12 Apr '22

12 Apr '22

I added a new routine to TEI/P5/Utilities/ called namespaces.xslt that generates a table that gives you counts of namespace nodes. See https://bauman.zapto.org/~syd/temp/4TEICouncil/namespaces_in_P5.xhtml.

1 2

Call in 25 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Apr '22

08 Apr '22

Here is the agenda: https://docs.google.com/document/d/1raASYeayA9dzeEWcvi1Zk17UGQAoqgnc-W8nbw4… Best, Martina

1 0

Next meeting: April 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Apr '22

06 Apr '22

Dear all, Our next meeting is on Friday, April 8 at 7am PDT / 10am EDT / 4pm CEST. Please add open issue/PR's to the agenda that we need to discuss for the release: https://docs.google.com/document/d/1raASYeayA9dzeEWcvi1Zk17UGQAoqgnc-W8nbw4… I'll add to the agenda tomorrow. Best, Martina

1 0

faster testing
by Bauman, Syd 06 Apr '22

06 Apr '22

One of the reasons the test procedure in Stylesheets/Test2/ is dramatically faster than the one in Stylesheets/Test/ is that it is, by default, run in parallel.[1,2] You can also ask the make command to run multiple jobs at once. The switches that control this are --jobs= and --output-sync=. I just tried an experiment, comparing how long it took to run make vs make --jobs=7 --output-sync=lines. (I chose 7 because my system has 8 threads, and I wanted to have some CPU available. What little I have found on the web seems to suggest I may as well go ahead and use 8.) The result was faster, although not even close to 7 times faster: down to 03:32 from 04:36. I compared the output of the 2 commands, and they were identical. On GNU/Linux, at least, the nproc command will tell you how many threads are available. Thus using the command $ make --jobs=`nproc 2>/dev/null || echo 1` -Oline seems to make sense to me. (-O is shorthand for --output-sync=.) It is also possible to get the Makefile to do that on its own. My first thought is that might not be such a good idea, because you may want to run with --jobs=1 in order to force error messages into the right order. (I.e., in case -Oline wasn’t good enough.) I ran the experiment again, this time using --jobs=8 and getting screen captures of the process monitor roughly 40 s after the make command started.[3] The timing results were very similar (down to 03:36 from 04:36), but the order of output lines was different. (Same output; i.e., they were identical after sorting and removing timestamps.) So I think anyone running the Stylesheets test process would do well to use the --jobs switch. You could use any of * -j 8 # if you know you have 8 threads, e.g. * --jobs=`nproc` # if you know the nproc command works on your system * -j `nproc 2> /dev/null || echo 1` # if there is a chance nproc fails, so it defaults to '1' Martina — could you either update the notes we have about updating P5 subset, or remind me where they are and I will? Thanks. Notes [1] ant test runs them in parallel; if you want them in series (likely because the order of messages was confusing when run in parallel) use ant testSeries. [2] There are other reasons, like it is written to be less redundant, and the JVM is only spun up once, rather than once for every test. [3] For evidence as to why --jobs makes make faster, see https://bauman.zapto.org/~syd/temp/4TEICouncil/Screenshot_of_make_process_m… and https://bauman.zapto.org/~syd/temp/4TEICouncil/Screenshot_of_make_-j_proces…

2 1