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

link rot
by Lou Burnard 11 Apr '21

11 Apr '21

There used to be a useful table listing the dates and version numbers of all TEI P5 releases at http://www.tei-c.org/Guidelines/P5/index.xml#previous <http://www.tei-c.org/Guidelines/P5/index.xml#previous> But now it seems to have disappeared. Could you either put it back or tell me where it's gone?My ODD chaining tutorial is broken without it.

2 1

Today's release preparations
by Martin Holmes 09 Apr '21

09 Apr '21

Hi all, Today Janelle, Martina, Nick, Syd and I in various combinations got this far with the new release: - Created new point-release branches for the TEI and Stylesheets repos. - Cherry-picked the fix commit into the P5 branch. - Added new release notes for this P5 release, and updated the two VERSION files. - Built the P5 branch in various places and confirmed it was good. - Took the p5subset from that branch and put it into the Stylesheets point-release branch. - Built the stylesheets and fixed all the many issues in tests resulting from the new p5subset. - Merged both these branches into the respective -released branches. Those branches are now building on the Jenkinses, eg: <https://jenkins.tei-c.org/view/TEI%20stable/> and when all those builds are complete, we'll have products we can use to create the release itself. The plan is for some of us to reconvene tomorrow if possible (Nick, Syd says he's available to help if you can arrange times). Anyone is of course welcome to ride along with the rest of the release process to learn how it works. I believe we will be starting from point 13, "Log into TEI server and run the tei-install.sh script", on TCW22: <https://teic.github.io/TCW/tcw22.html> Some time next week, once the release is done, Hugh and I should get together with anyone else who wants to learn the process and do the Oxygen plugin release, updating point 23 in TCW22 as we go. Anything I've missed? Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

Call today
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Apr '21

08 Apr '21

Dear all, This is the agenda for our meeting today (11am PDT / 2pm EDT / 7pm BST/ 8pm CEST) https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… and the zoom link https://us02web.zoom.us/j/82014974946?pwd=OVZXbTNkU1kyWGhEOUR3VWh0WUF3dz09 Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Dienstag, 6. April 2021 16:25 An: tei-council(a)lists.tei-c.org Betreff: Next meeting: April 8 Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Fairly urgent bug in recent releases
by Martin Holmes 06 Apr '21

06 Apr '21

Hi all, Janelle and I came across a bad problem with releases starting at 4.0.0, which means that valLists for the @type attribute in 21 elements are missing from both the Guidelines pages and the schemas. There's a bug here: https://github.com/TEIC/TEI/issues/2128 and a PR with a full fix here: https://github.com/TEIC/TEI/pull/2129 Both Syd and I think this is bad enough to warrant an interim release. Could anyone with a free moment take a look at the bug and the PR, and review or comment? Also, could you weigh in on whether you agree that it deserves a quick release? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

6 8

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

06 Apr '21

Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Council meetings missing from google calendar
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Apr '21

01 Apr '21

Dear all, Jessica brought to my attention that the dates for the regular Council meetings are missing in our shared google calendar (even the past meetings). I don't know how this could have happened. I have added the dates again, our next meeting will be on Thursday next week, April 8. Best, Martina

1 0

Stylesheets meeting today, Thu 25 Mar
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Mar '21

25 Mar '21

Dear all, please find the google doc for our Stylesheets meeting here: https://docs.google.com/document/d/1Qolxk9yzIAtqofcu7szuPArOuv1koy6g-bjhM1r… Meeting times: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) Zoom link: https://zoom.us/j/95354913465?pwd=ODZpVUxFVmJjWnlIZnBnaCtIVnFadz09 Best, Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Bauman, Syd Gesendet: Mittwoch, 24. März 2021 04:09 An: tei-council(a)lists.tei-c.org Betreff: Re: [Tei-council] upcoming Stylesheets meeting, Thu 25 Mar Topics for discussion, in no particular order: * 2-minute update on Saxon 9 -> Saxon 10 (MH) * Did we have more to discuss or work on for PR #327<https://github.com/TEIC/Stylesheets/pull/327>? (I forget) * Close issue #272<https://github.com/TEIC/Stylesheets/issues/272> and create new ticket for @mode? * Didn't we fix #482<https://github.com/TEIC/Stylesheets/issues/482>? * Issues we have started delving into, but have not solved: * Issue #327<https://github.com/TEIC/Stylesheets/issues/237>, generating an element or attr that has the same local-name as a TEI element or attr * Issue #402<http://We%20need%20a%20volunteer%20to%20write%20a%20test%20ODD>, on @mode: we need a volunteer to write a test ODD * Issue #399<https://github.com/TEIC/Stylesheets/issues/399>, <code> being dropped from <desc> * Issues that have had a lot of work done, but still are not fixed: * Issue #444<https://github.com/TEIC/Stylesheets/issues/444>, <desc> getting dropped * Issue #102<https://github.com/TEIC/Stylesheets/issues/102>, for which we now have test output, and I finally sort of understand the problem * Issue #424<https://github.com/TEIC/Stylesheets/issues/424>,@ns causing pain ________________________________ We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 1

upcoming Stylesheets meeting, Thu 25 Mar
by Bauman, Syd 24 Mar '21

24 Mar '21

We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 2

git me this
by Bauman, Syd 23 Mar '21

23 Mar '21

I have on my local HD a copy of a fork one of our repos.[1] The interesting bit of this repo is in its dev branch. But sadly, its dev branch is somewhat behind our dev branch. So I would like to merge our dev branch in. How do I do that? I.e., how do I specify that I want the git merge command to use our repo’s dev branch (not the current repo’s dev branch, which would be silly, as I am on the current repo’s dev branch) as the upstream? Note [1] https://github.com/sanskrit-coders/Stylesheets.git to be precise, but that detail does not matter.

2 4

p5subset.xml and TCW22
by Martin Holmes 12 Mar '21

12 Mar '21

Hi all, Syd, Nick and I were looking at the Stylesheets repo this morning and we realized that the version of p5subset.xml in its source subfolder had not been updated for quite a long time. That means the Stylesheets tests were running against an old version of the Guidelines. When we decided to put p5subset.xml into the Stylesheets repo, the purpose was to avoid the circularity problem that causes an inability to build each repo against the other. That's been successful, but the corollary was that we should regularly update the p5subset.xml in the Stylesheets repo so that we caught new issues resulting from changes to the Guidelines in good time. That hasn't happened. We added an updated p5subset.xml this morning, and there were a LOT of test issues to fix, although none of them were significant. We've added two new steps to TCW22 so that at the beginning of the freeze or refrigeration period[1], an up-to-date p5subset.xml is added, meaning that almost everything will get fixed at that point; and then later, once the release-X.X.X branch of P5 is building, the p5subset.xml from that gets added into the release-X.X.X branch of the Stylesheets, so that our release is actually coordinated (the states of the two repos match), prior to the release. In the process, we also noticed that lots of the instructions about creating the release-X.X.X branch were written to apply ONLY to the TEI repo, but the same steps also have to happen for the Stylesheets repo, so we've made that more explicit. In our regular Friday meetings, the three of us are going to make a point of updating p5subset.xml so we don't get so far out of sync again. Anyone else is also free to update it any time of course. Cheers, Martin [1] TCW22 doesn't adequately distinguish these two phases; we should fix that. -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0