Closed Bug 1703253 Opened 4 years ago Closed 3 years ago

update to Django 3.2

Categories

(Tecken :: General, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

(Blocks 1 open bug)

Details

Attachments

(4 files)

Tecken uses Django 2.2 because that was an LTS. Today, Django released 3.2 which is the new LTS.

https://docs.djangoproject.com/en/3.2/releases/3.2/

Django 2.2 is supported until 2022, but there might be a compelling reason to update sooner than that.

Grabbing this to do. Making this block the GCP migration because we need to rewrite the storage interface and I'm thinking we should update Django first.

Assignee: nobody → willkg
Blocks: 1687804
Status: NEW → ASSIGNED

Bumping bugs off my queue because I'm not going to get to them any time soon.

Assignee: willkg → nobody
Status: ASSIGNED → NEW

willkg merged PR #2489: "bug 1703253: upgrade to django 3.2" in faf2e3f.

Once this deploys to stage, I'll go through the webapp and API.

It deployed to stage and I went through things and everything looks ok to me except the admin part of the site.

Django redid the admin structure, so the pages that we added to the admin work, but render a little weirdly. I'm the only one who sees it, so I'm going to push it off fixing it to another bug.

willkg merged PR #2497: "bug 1703253: update django to 3.2.12 and add migration status to site settings admin page" in a2559df.

This fixes the admin. It also adds the db migration status, so I can see what the situation is in order to redo how I did autofield.

I deployed this to prod earlier today in bug #1753441. Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: