-
-
Notifications
You must be signed in to change notification settings - Fork 168
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
New release? #72
Comments
All our builds are passing. As long as Django 1.9 is not stable don't expect it to be added to the build matrix. What is crashing? Can you post a stack trace? Can you provide a PR? |
Django 1.9 has already been stabilized, and is currently on rc1.
|
I'd recommend you add 1.9 to the build matrix, and we see what happens. If all goes well with the code as it is. Your PR is appreciated. As soon as 1.9 is officially out we'll merge that into |
I've added 1.9 to the dependency matrix (along with py35 which was also missing, and has been release for some time now). Hopefully this can be merged in and a new release can be made? :D |
+1 |
@brainrape See our Gitter chat. Joost must take a decision on the version number. We're getting there. |
Thanks |
Finally release version 2.0.0 that is compatible with 1.9 thanks to @hobarrera. |
It's been a while since the last release, and the latest
master
crashes with django19 (which is at rc, and will be release in less than a couple of weeks).Can we get a new release (1.0.1?), that's django19-compatible? :)
The text was updated successfully, but these errors were encountered: