-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Release 1.1.2 with WCSLIB 5.14 and also 1.0.9 #4613
Comments
That sounds good to me! |
@astrofrog - I've double checked and 1.0.8 seems to show none of these precision-bouncing effects. |
See #4619 for a clarification of the changelog and another regression test. |
Note that everything that should be seems to be backported to v1.1.x now, and the only holdout is that #4561 needs to get in to restore py2.6 compatibility. |
@astrofrog - OK, I think everything is backported that should be for 1.0.x and 1.1.x. And v1.1.x is passing: https://travis-ci.org/astropy/astropy/builds/112699046 We do need to do some changelog cleanup, though. I also think it would make sense to try to get #4650 in before a release, as it fixes some unintended consequences beyond astropy that were reported in #4633. |
Also now v1.0.x is passing following a changelog tweak: https://travis-ci.org/astropy/astropy/builds/112746614 |
Current TBD before release:
Note that I also changed the title to do 1.0.9 at the same time. That will make the changelog easier anyway. |
1.1.2 released! https://pypi.python.org/pypi/astropy/1.1.2 |
As described in #4579 (comment), there is a major bug in the WCSLIB bundled with Astropy 1.1 and 1.1.1 which caused #4612. This is fixed in master by #4579 but should be backported to the 1.1.x and we should then release 1.1.2, since this is a bad bug (CRVAL1 gets truncated to ~arcminute precision!).
cc @keflavich @nden @eteq
The text was updated successfully, but these errors were encountered: