Django-rest-framework: Version 3.11

[tomchristie]

Just opening this issue to track what we think is required for 3.11.

I've been spending a lot of time on the ASGI ecosystem stuff lately so not fully up to speed here, but looks like https://github.com/encode/django-rest-framework/pull/6172 is one of the big ones we need to get resolved.

Anything else need to go on the list? Anything related to OpenAPI?

I could also put some working into sharpening up this API docs tooling now that we've dropped the Core API approach, depending on if it would tie in nicely with 3.11

[carltongibson]

Anything related to OpenAPI?

There are a couple of PRs on my list. #6865 in particular, which looks fine, but just needs the requisite _moment_. Anything else you see, just ping me for a review.

[tomchristie]

Gotcha. I guess targetting the end of this month might be a good plan?
Probably wouldn't need a whole lot of work to get it squared away.

[carltongibson]

For me, a week or two is fine (if you give me a few days _heads up_ 🙂) so if EOM suits you perfect!

[tomchristie]

I'm planning to get back onto this from Friday - we might be able to plan for a release sometime mid-month.

[rpkilby]

Should we hold off until early December when Django 3.0 releases? Per the recommendation in the release notes, it would be a good time to drop support for everything below Django 2.2

[auvipy]

Django 3 release candidate is pretty close. may be in 3/4 days. drf should be working with it. IMHO, 3/4th week of November would be great.

[rpkilby]

I'm more discussing what versions DRF 3.11 should support, as it isn't ideal to change supported versions in patch releases (e.g., don't want to add 3.0/drop 2.0 support in DRF 3.11.1). We could:

• Wait until December for Django 3.0, then support Django 2.2 and 3.0
• Go ahead and release soonish, preemptively supporting Django 2.2 and 3.0rc1
• Release soonish, supporting Django 1.11, 2.1, 2.2

[tomchristie]

I don't neccessarily agree that Django's third party "we suggest that third-party app authors drop support for all versions of Django prior to 2.2" is appropriate for us.

I think it'll make sense for us to release just after the 3.0 release candidate becomes available. I'm planning to have a look at first thing next week. We can take a view onto which versions we'll support once we know if there's any awkward compat cases.

[carltongibson]

There's a lot of folks who'll use the 1.11 LTS until it's EOL in April 2020. Given DRF's position, if there are no compelling reasons to drop support, I'd argue to support 1.11 until then. (i.e. Support all supported versions of Django, as a rule-of-thumb.)

[Kentalot]

Hi all, just wondering what's status on 3.11? Waiting for a fix that's merged in. Would like to use official release. Thanks!

[tomchristie]

@Kentalot - Soon. 👍

[tomchristie]

Righty, we just need to get the release notes written up.
Planning on getting this sorted this week.

[auvipy]

a new release before this week ends would be awesome :)

[napsterv]

I hope it gets released next week.

[tomchristie]

Chill. It’s coming.

[auvipy]

the simple router based on django 2.0+ should be in 3.11 as all new projects starting will use django 2.2+

[tomchristie]

Closing this issue in favour of PR #7083