We are preparing for the Sumac upgrade, and one of the important steps of the upgrade, is tracking and rebasing existing code drift. For that we heavily rely on the Code drift dashboard. However, it’s not fully automated, and currently only automatically detects open PRs against the edx-platform repo. We are planning to improve the automation.
However, right now it is important that all the PRs that haven’t been merged upstream into sumac.master or sumac.1 are present in the dashboard. I’m asking all client owners (mostly from @bebop) to check all the code drift that exists for the clients that you manage and make sure it’s added to the dashboard.
If you’ve updated the maintenance information correctly (there was a ticket for everyone recently), it should be easy to check the code drift section against the dashboard.
If in doubt, please follow the process outlined in “How to handle Code Drift” section of our handbook, or ping me.
It also may be that the repository that contains the code drift is not listed in the dashboard. In that case, it has to be added manually. Let me know if there are any issues with that.
I think all the code in the eshe-mvp branch for the android app is also code drift that needs to be resolved now that a new version of the app is released. It is not going to be an easy rebase unfortunately, but we’ll probably need to do it with the next version of the platform and app.