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
Cut a release compatible with Django 1.11 #1490
Comments
I wasn't sure I had the ability to publish to PyPI, but evidently I do now. I'll have a look later this week to see what PRs can be merged and then cut a release for 1.10. @adamzap If you feel like helping, you could have a look at open PRs and comment on those that seem possible to include in the release. If you don't have time, that's fine, but if you do that'd speed things up a bit. |
Sure! I took a look at all PRs assigned to the However, I think #1485 can be merged immediately since it's a simple documentation fix, and #1320 can be closed since it includes no changes. Let me know what you think. I'll keep looking around. Are you on IRC somewhere? Maybe we can chat about how I can be more helpful. Also, thanks to my employer, Crossway, for allowing me to spend work time on this! |
The milestones are pretty much meaningless, I assigned issues to them as a way of prioritizing them for myself, but I haven't had time to work on those releases. Generally speaking, 0.13.4 issues should be done before 0.14.0 issues and are less likely to break backwards compatibility, so they should still be kept separate. The 1.0.0 milestone was there before I joined, some of them maybe should be moved up in priority. |
I'd like to do the same and just close them due to inactivity, but a lot of them are for legitimate bugs so we need to keep a record of them. |
Any news? |
Following up on this. |
Following. |
1 similar comment
Following. |
Please just hit the "Subscribe" button to follow this thread. If you comment, you notify everyone else that you're subscribing. We're all interested :) |
Any plans to support Django 1.11? https://www.djangoproject.com/weblog/2017/apr/04/django-111-released/ |
It seems there are Django 1.10 compatibility fixes that landed in master. It would help if someone could confirm whether tastypie master branch has issues with 1.11. |
What's the status on this? Thanks. |
in Django 1.11 we have problems too, please update compatibility for django 1.11 |
TODO: Release notes:
Tests:
Fixes left to do:
|
@georgedorn I'm happy to rebase #1486 or do whatever else needs doing to get things moving again. |
Is tastypie supporting Django 1.11? |
Release v0.14.0 was just uploaded to PyPI. It includes explicit support for LTS versions of Django (1.8 and 1.11). Django 1.9 and 1.10 almost certainly are compatible, but are unsupported. |
Any chance we could get an official release since #1480 was merged?
Thanks!
The text was updated successfully, but these errors were encountered: