-
Notifications
You must be signed in to change notification settings - Fork 629
Description
Is your feature request related to a problem? Please describe.
Currently python.org is running on top of Django 2.0.13 to which the support was dropped on April, 2019. Besides of don't getting security or other updates from other LTS versions, it also makes harder for the project to use most recent versions third-party apps.
Describe the solution you'd like
To upgrade Django to 2.2 since it's a LTS one and will have support until April 2022.
Describe alternatives you've considered
Even though we already have Django 3.2 LT version, I think upgrading to Django 2.2 is a good initial step on upgrading directions. Also, we can only think about upgrading to Django 3.2 LTS after going through the 2.* upgrade pipeline.
Also, I think this process will help us to understand the consequences of such upgrade with a smaller step and, thus, better prepare ourselves for the desired Django 3.2 upgrade.
Additional context
During this process, we must consider eventual backward incompatibilities introduced by Django 2.1 and 2.2 and address them. Here's the link to both lists:
From what I've already seen, upgrading Django itself won't be a problem. The biggest chunk of work will be to update the Django third-party libraries used by Python.org. They can be found on base-requirements.txt
and dev-requirements.txt
.
If you're new to the project, please read our install instructions to run it locally on your computer. You can tag me (@berinhard) or @ewdurbin for any doubts or questions on this process.