Zenodo version behind

[rettinghaus]

The version published on Zenodo is still on verion 4.7.0. It should always reflect the latest version.

[peterstadler]

This is something I've done voluntarily without official approval by the TEI Council, i.e. it's not documented in the release process. Iff Council wants to take over official responsibility there's actually not much to do but

1. release technicians would need to register with Zenodo and need to get access to the Zenodo repo
2. this step would need to be written down in TCW22

For the meantime I will add the missing releases asap.

[laurentromary]

Hi. May I ask what the use case is to put a release in Zenodo? GitHub is automatically harvested by Software Heritage and thus long term archived + allocation of a SWHId. It sounds superfluous, but I would be happy to hear that it has an added value. Laurent

[peterstadler]

I didn't know about Software Heritage but from looking at https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/TEIC/TEI it seems they only archive the repository without the release artifacts.

Additionally, I like to have these things stored redundantly.

[laurentromary]

I would suggest to get into this if you plan to have a systematic archival strategy.