How to Move to Django 3.2

One of our challenges at X is that we use something like 150 different third-party packages to build upon. We're in the middle right now of moving to Django 3.2 from 2.2. Many of them are not because these packages, you know, they get stale. And then we have to decide, can we get rid of that package? Can we live with it the way it is? Do we have to fork that package?