Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zenodo version behind #2670

Open
rettinghaus opened this issue Jan 26, 2025 · 4 comments
Open

Zenodo version behind #2670

rettinghaus opened this issue Jan 26, 2025 · 4 comments

Comments

@rettinghaus
Copy link
Contributor

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

@peterstadler
Copy link
Member

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
Copy link
Contributor

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
Copy link
Member

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants