TEI Technical Council Teleconference, 2023-11-10

6:30am PST / 9:30am EST / 2:30pm UTC / 3:30pm CET

Nicholas Cole (NC) Mentoring new Council members

November 5–10 refrigeration, Thurs. Nov. 16 release.
release technicians: RV, HC, and GR
Is the information regarding the incrementation of the release numbers written into TCW 22 somewhere?
- Action on EBB or RV: Add something to TCW 22 about the automagic updating of specLists.json
Be sure before release to update Preface and Acknowledgements with new Council members. Also add information about the working groups may need to double check with Syd. Action on MS and EBB to collaborate on this.
For example, 5.0 would be for when something significant occurs like a chapter is removed or a new one added

Shouldn’t be entirely automated to “punt” tickets to next release if not closed
But if PR is closed it should be assigned to the current milestone (if this could be automated that would be helpful.

HCMC Jenkins build broken

looks like a problem with rng/to.xsl:
https://teijenkins.hcmc.uvic.ca/job/TEIP5-dev-all-with-Stylesheets-release/
Was fixed but HCMC Jenkins broke again after a RELAX NG change
This won’t pass until after the release.
dev with dev should work; release with release must work; dev with release won’t work yet …
Schedule a session on best practice for testing branches for the virtual F2F for all Council members to make sure they are up to speed.
Tests are being renamed to ensure that Council members know what the tests do

The ePub3 problem…
- Solved — I (SB) had failed to limit the XPath to "atts" classes.
SB & RV merged quite a few PRs and made other fixes yesterday. Remaining tickets to consider include
- Stylesheets 525 - already merged
- Stylesheets 615 — merged!
- Stylesheets 618 — merged! milestone added to the related issue.
- TEI 2440 - already merged hurrah
- TEI 2450 - RV resolving conflicts and merging PR. — merged!
- TEI 2470 let’s try and look at this closely for this release — merged
  - Proposed change is mostly text related so should not break the build
  - Prose only mentions p and not ab, a simple commit and push to dev to update the prose accordingly to solve this. Action on MS to do this today after the Council meeting.
- TEI 2500 — merged!
  - TEI conformant document, what does this entail exactly?
  - Chapter needs revision
  - This PR does not address everything on the original issue #2179, just one aspect of it.
- TEI 2276 RV is okay with SB and TOC working on this for 4.7.0 release before Tuesday and do a PR — DONE, see #2501 - merged
- 2447 to be resolved also for 4.7.0 Action on TOC.
#2447 Ling SIG related ticket, an easy fix for release 4.7
- Add release techs and SB to PR to push this through to the release.

E Editiones society has had a call for someone to come and work on the project, Rolf Wissman is working on it and will be working on the council and joining Council discussions to discuss TEI Lite

EBB arranged poll about modality of the F2F:Result: Roughly equivalent time of F2F in 2–2½ VF2F meeting sessions.
Action on EBB: Arrange second poll to help figure out when to do the VF2F sessions. Maybe do one in winter, stretched out over a few months rather than concentrated. Having all of them in May is too late.

Paused while transfer team tries to figure out if pointers to archives at Brown can be mapped to their new location at PSU.
Found 3 different kinds of URLs and figured out how to map those.
Permalinks problem
Archive problems sorted out in January and resume mailing transfer after that.

The kinds of changes Council makes that affect only ODD writers: usually we list breaking changes in our release notes, but don’t do a deprecation
We asked the community–should there be a deprecation period? (No one answered.) So since everyone was quiet, Council agrees, we think we don’t really need to deprecate.
JT suggests we add an “ODD-breaking” label to the issues about this. (Consensus agreement) — He will be adding it to his re-vamping of issue labeling per Paderborn.
SB suggests also having a separate section in the release notes of ODD-breaking changes are useful. (Consensus agreement)
RV: Adjust the TCW 22 & 27 (about deprecation) accordingly. (For changes that break ODD but don’t break anything else.) Action on RV to describe this in the issue with a comment.