-
Notifications
You must be signed in to change notification settings - Fork 49
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
Update to SOFA version 13 #45
Comments
We should -- but I fear I won't be able to do it... |
@bsipocz @mhvk - we could pull it into master today (and pull it into Astropy), but I don't think I can do the full release. So it depends on whether we want a "pre-released" version in Astropy. (We'd still have 2 weeks to iron out any changes, since those could be post feature-freeze but pre-Astropy release). I don't see that as a new "feature". @astrofrog or @taldcroft might want to weigh in too, given that it's an Astropy procedural question |
I feel that your proposal is fine for feature freeze, given if you can do a full release before we have final v2.0. (Updating externals doesn't seem to be a new feature to me, but erfa is critical enough that we need the RC testing for it I think.) |
Agreed with @bsipocz - pre-release should be fine. I think it would be very good to have even just the erfa version exposed in astropy 2.0. |
As noted by @rmathar (#44 (comment)), SOFA version 13 is out, and we should update ERFA to it, since it solves #40 and #41. It is also a good opportunity to finally get in #42...
The text was updated successfully, but these errors were encountered: