Arbi-BOM notes: /wiki/spaces/AT/pages/3297313270
Django 3.2 upgrade overview: Django 3.2 Upgrade
MySQL 5.7 → 8.x upgrade should probably be done before the next major Django upgrade
What should we continue doing?
...
Share IDA specific expectations and desired timeline before hand to help owning team to plan
Give the owning team guidance and examples for upgrading IDAs
The use of a shared common library constraint file
Allowing the deploying smoke testing be done by the owning team
Use of slack to help owning team’s questions and problems.
Involving community was a good decision for packages upgrade.
What should we stop doing?
TBDI cannot remember if this is true, but I thought the django 3.2 upgrade and migrating from Travis to github actions happened really close to each other. That’s a bit confusing in the beginning
What should we start doing?
Introduce the Archi-bom team to rest of the engineering organization. Faces and names. I do feel like in the beginning, I don’t really know what stake Usama and Muhammad had in this effort until pretty late in the tasks.