...
Counting the service’s dependencies which use Django
Determining how many of those dependencies still don’t support Django 2.2 in their latest release
Determining how much edX-managed code needs to be updated for Django 2.2 support
Determining how much work would be involved in fixing/forking/replacing external dependencies which don’t yet support Django 2.2
Estimating how much work will be needed to update the service itself based on its size.
Additionally, This is the actual list of services which we know need to be updated needs to be fully enumerated.upgraded from Django 1.11.x to Django 2.2.x, along with a recent count of the number of kilobytes of Python code in each repository (excluding dependencies) which may be useful as a rough starting point for estimation:
edx-platform - 23,423 KB (dependencies dashboard)
ecommerce - 3,109 KB (dependencies dashboard)
course-discovery - 3,052 KB
edx-analytics-dashboard - 662 KB
credentials - 458 KB
registrar - 444 KB
edx-analytics-data-api - 355 KB
xqueue - 137 KB
portal-designer - 119 KB
edx-notes-api - 108 KB
openedxstats - 101 KB
api-manager - 34 KB
4. Hire an appropriate number of outside contractors
...