Repository navigation
Release final 1.1 version #3519
Description
NOTE For now these are just major issues ported over from 1.0 that were not completed - we should review and edit these at a later time:
Integration of units:
- Implement masked quantities (Implement MaskedQuantity #1852) - @adrn @mhvk
Coordinates, Time, and Observatories:
- automate
IERSupdates (Automate updating IERS_B and LeapSecond files whenever a release is made #1697) and other data with expiration dates. @mhvk @taldcroft @eteq - barycentric coordinates and velocities, ideally at VLBI precision (if things go quickly enough)
Stabilize modeling API:
- implement support for Quantities(Models should support Quantity #1464) @nden @embray @wkerzendorf
- add 'default_fitter', 'last_fitter' and 'fit' method to models (Add a
fitmethod to models #1330, Store fitter object in model object #979) @nden @embray @wkerzendorf - add support for getting uncertainties on parameters (Add support for returning uncertainties on fit parameters in astropy.modeling #1827)
Miscellaneous:
- Implement any backward-incompatible API changes needed for the future generalized WCS (even if the full thing isn't implemented) - @nden @perrygreenfield @jehturner
- Remove things scheduled for removal, in config, units and utils. (Comments of "REMOVE in astropy 0.5" #3500).
-
⚠️ We need to update the contributor list!⚠️
In addition, the following documentation/help-related issues should be addressed:
- Implement a help system tied to exceptions/warnings - @demetri
Lower priority issues
- Better integration of FITS tables and VO tables with the Table class - @mdboom @taldcroft @embray
Activity
astrofrog commentedon Oct 15, 2015
astrofrog commentedon Nov 9, 2015
Individual commits that should be backported:
astrofrog commentedon Nov 17, 2015
Need to update the number for issues/pull requests/contributors at the last minute
embray commentedon Dec 3, 2015
I think maybe this issue should be renamed to "1.2" and moved to that milestone, with a new issue similar to it created for 1.1. That or make one for 1.2 and move a bunch of the above checkboxes over to it.
It's just funny because almost none of the checkboxed items in this list are going to be done in the v1.1 release, since other priorities came up.
mhvk commentedon Dec 3, 2015
A new issue is better I'd think...
Before starting that, it would be quite helpful to discuss missing pieces in astropy, and perhaps assign some priority to them. But perhaps it is best done first on a wiki page?
eteq commentedon Dec 4, 2015
@mhvk @embray - how about we close this one when the final release is done (as we've done for past releases), and then move these to a new issue for v1.2. We can then use those as a starting point for a developer hangout to discuss priorities.
embray commentedon Dec 4, 2015
@eteq Unfortunate, but sounds good.
mhvk commentedon Dec 4, 2015
Yes, makes most sense. And we did get quite a bit done for 1.1, so I'm not going to feel too bad. Though we also need to think about how to get a few more contributors...
eteq commentedon Dec 4, 2015
Actually, I don't know that contributor growth is a problem per se, @mhvk (see the plot below)... But we do need to get some of them more involved in "deep-dive" issues, I think.
mhvk commentedon Dec 4, 2015
That's very encouraging indeed! Possibly we can get a few more by asking specifically for "seconds" and "thirds" for the different modules (definitely needed for
units...)embray commentedon Dec 4, 2015
That's total cumulative # of contributors so of course it always goes up. Would like to see # of new contributors per , and also # of contributors with, say, > 50 commits.
eteq commentedon Dec 8, 2015
Yes, it definitely has to go up or stay flat, but the point I'm making is that it is continuing to go up.
The other two are interesting questions, though - the code I used to create the plot above is at https://github.com/astropy/astropy-tools/blob/master/astropy_status_plots.py (the
commiters_plotfunction), so anyone is welcome to try teasing out more analytics like that...astrofrog commentedon Dec 8, 2015
I think it'd also be interesting to make a plot of the number of contributors in a moving window of say 6 months (but I also don't have time to try that out!)
embray commentedon Dec 8, 2015
Incidentally, my sadly neglected "blog" has a post about using Pandas and
git logto generate statistics about git repos, if anyone wants to play with this: http://iguananaut.net/blog/programming/git-logs-in-pandas.htmleteq commentedon Dec 11, 2015
Release done! https://pypi.python.org/pypi/astropy/1.1
taldcroft commentedon Dec 11, 2015
🎆
embray commentedon Dec 12, 2015
¯_(ツ)_/¯
bsipocz commentedon Dec 12, 2015
🎉 for 1.1