...
We expect the workflow to be something like the following, although we may make some improvements to the process as we go:
An issue will be created in the We have created an issue for each particular task in https://github.com/edx/upgrades/ repository and added to the project board for a particular taskissues and tagged them with a yellow “outdated dependency” label. If you think of an appropriate task that hasn’t been ticketed yet, please go ahead and create a ticket for it.
When you’re ready to start actively working on a task, please add a comment to that effect. Someone at edX will then assign the ticket to you and update the ticket status on the board.
If a usable new upstream release is created for a dependency, please mention it in the ticket so the status can be updated. If you create one or more PRs for review, please mention those in the ticket as well.
Open edX services will upgrade to newly released dependency versions during routine dependency upgrades and active work on updating the services to work with Django 3.2
If you have any questions, please raise them in the Open edX #external-openedx-django-3-2 Slack channel.
You can see current status of dependencies work in this diagram.
...