Re-enable Zenodo for citable releases

[hugovk]

In #1322 we enabled Zenodo to create DOIs for Pillow releases, so it can be citable. And it's worked! We have some citations!

However, at https://doi.org/10.5281/zenodo.596518, we can see Pillow 3.0.0 and 3.1.0, but nothing newer.

@aclark4life Please could you check the settings? I don't have permission.

For example, at https://zenodo.org/account/settings/github/repository/hugovk/Pillow I can see:

How does https://zenodo.org/account/settings/github/repository/python-pillow/Pillow look?

General guide: https://guides.github.com/activities/citable-code/

[aclark4life]

@hugovk Any better now?

[hugovk]

I won't be able to see until we make the release next week. Is the switch now flipped?

[aclark4life]

@hugovk Copy that

[hugovk]

Thanks for the screenshot. Hmm, well at least it's been trying to do it for each release... I sent this to https://zenodo.org/support:

Hello,

We enabled Zenodo for the https://github.com/python-pillow/Pillow/ repository in 2015 (#1322), but it only created a DOI for two quarterly releases:

https://doi.org/10.5281/zenodo.596518

Looking at https://zenodo.org/account/settings/github/repository/python-pillow/Pillow, it shows it has been trying for each release, but says "Failed".

Here's a screenshot in our tracking issue: #4490 (comment)

Please could you let us know if there's anything else extra we need to get it working?

Thank you!

Hugo

[hugovk]

Reply from Zenodo:

Dear Hugo,

I apologize for this inconvenience.
I have now manually published the missing releases, as a notice, we found a duplicate event in our system for the release tagged as '6.0.0', please let us know if this was not from your side.
We plan on improving this feature since we are, sometimes, experiencing these seemingly random failures which can be frustrating for our users.

In the meantime, if you encounter any further issues or failed releases don't hesitate to contact us again.

Best regards,
George

https://doi.org/10.5281/zenodo.596518 now has all the other releases.

Any ideas what may have caused a duplicate event for 6.0.0? 6.1.0 had a hiccup with a tag deleted and retagged - #3835 (comment) - but 6.0.0 went out smoothly: #3618.

[radarhere]

There was a problem with building the Windows binaries for 6.0.0, so I could easily have retagged that release after the issue was fixed.

Did this work for 7.1.0?

[hugovk]

OK, that could have been it.

Yes, it worked for 7.1.0 and 7.1.1:

Closing, thanks!