-
Notifications
You must be signed in to change notification settings - Fork 24
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
Comments
@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...) |
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? |
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... |
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. |
closing since this is done except for making a pyerfa badge, which already has its own issue |
README.rst
(and don't expose it in docs...); fix by adding a badge in Authors and badges #43The text was updated successfully, but these errors were encountered: