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

Post-1.7.0 release nits #35

Closed
6 of 7 tasks
mhvk opened this issue May 31, 2020 · 5 comments
Closed
6 of 7 tasks

Post-1.7.0 release nits #35

mhvk opened this issue May 31, 2020 · 5 comments

Comments

@mhvk
Copy link
Contributor

mhvk commented May 31, 2020

@mhvk
Copy link
Contributor Author

mhvk commented Jul 11, 2020

@eteq or @astrofrog - could you enable third-party access so we can have pyerfa on zenodo? (I'm happy to do the actual linking, but it needs the access...)

@mhvk mhvk mentioned this issue Jul 11, 2020
@astrofrog
Copy link
Contributor

astrofrog commented Jul 11, 2020

I wasn't sure what was meant by 3rd party access but I've now made all PyERFA maintainers also be admins for the repo instead of just maintainers - @mhvk is that enough?

@mhvk
Copy link
Contributor Author

mhvk commented Jul 12, 2020

Yes, it is! Now set up to automatically be stored on zenodo once another release is made. The changes above may be good enough to warrant an 1.7.0.1...

@mhvk
Copy link
Contributor Author

mhvk commented Jul 12, 2020

Actually, turns out it is triggered by publishing on github, which I hadn't done yet (just had the tag), so just published 1.7.0 to be done with it. And #44 for adding the tag, so people have a DOI to cite.

@mhvk
Copy link
Contributor Author

mhvk commented Jul 12, 2020

closing since this is done except for making a pyerfa badge, which already has its own issue

@mhvk mhvk closed this as completed Jul 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants