List view
- No due date•68/68 issues closed
- No due date•38/38 issues closed
- No due date•11/11 issues closed
- No due date•112/112 issues closed
- No due date•323/323 issues closed
- No due date•50/50 issues closed
- No due date•18/18 issues closed
A release will be cut before the end of the month as the milestone contains critical fixes for the new JPL Horizons API, and the old API is expected to be turned off soon.
Due by October 22, 2021•44/44 issues closed- No due date•24/24 issues closed
- No due date•100/100 issues closed
- No due date•56/56 issues closed
- No due date•29/29 issues closed
- No due date•98/98 issues closed
We'd like to have continuous deployment working so we don't have to make versioned releases to get stuff to users via pypi.
Due by June 1, 2018•3/3 issues closed- No due date•83/83 issues closed
- No due date•2/2 issues closed
- No due date•47/47 issues closed
- No due date•48/48 issues closed
- No due date•38/38 issues closed
- Due by October 11, 2016•33/33 issues closed
- No due date•50/50 issues closed
- Due by November 21, 2016•25/25 issues closed
Fixes to Version 0.2
Due by August 31, 2014•1/1 issues closedVersion 0.3 release
Due by November 21, 2014•6/6 issues closedRelease schedule set to follow astropy 0.4: https://github.com/astropy/astropy/wiki/Release-Calendar
Due by May 27, 2014•33/33 issues closed- No due date•32/32 issues closed
We want releasable code! * Requires uniform API * Must pass tests * Must have at least the basics fully functional (NED, Simbad, IRSA).
Due by August 20, 2013•36/36 issues closedWe need to get a complete travis grid working before we can really be sure development is proceeding sanely. Key goals are to clean up the docs and ensure py3 compatibility
No due date•1/1 issues closedOur first major milestone before any sort of reasonable release is to create a uniform API.
No due date•4/4 issues closedPython 3 compatibility
No due date•1/1 issues closed