Skip to content
This repository has been archived by the owner on May 5, 2020. It is now read-only.

Decide which django releases that should be supported #52

Closed
relekang opened this issue May 16, 2015 · 1 comment
Closed

Decide which django releases that should be supported #52

relekang opened this issue May 16, 2015 · 1 comment
Milestone

Comments

@relekang
Copy link
Owner

Django download page has a list of supported versions.

@relekang relekang added this to the 2.0.0 milestone May 16, 2015
@ataylor32
Copy link
Contributor

For what it's worth, here's an excerpt from a post on the official Django blog:

Q: I’m the maintainer of a reusable application. Which Django versions should I support?

A: We recommend that you support the same Django versions that are supported by the Django team. With the new deprecation policy, it should be possible to support two consecutive LTS releases (e.g. 1.8 and 1.11) and all the non-LTS versions in between without requiring backwards-compatibility shims in your own code, as long as your code runs warning-clean on the lower LTS (1.8), because any non-deprecated feature in one LTS release is guaranteed to remain in place through the next LTS release.

@rubengrill rubengrill mentioned this issue Jul 22, 2018
@relekang relekang closed this as completed Mar 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants