Page Comparison

Start Recording

Mongo Upgrade

• Planning on not testing Mongo 4.4 with Python 3.11

• Main 2U SRE Contact - Muhammad Nadeem Shahzad

Python Upgrade

• Arbi-Bom is fully working on the Python Upgrade so they will be ready to ship it as soon as it’s ready.

• edx-platform has 3.11 testing for all github workflows that could have it.

• All relevant package updates are coming with updates to the github issues here: https://github.com/openedx/edx-platform/issues/34229

  • And most package updates are going in one at a time now.

• Edly volunteered to help with ecomm and ecomm-worker: https://discuss.openedx.org/t/these-idas-will-not-be-upgraded-to-python-3-11-by-redwood/12755/3

Node Upgrade

• Still in progress Brian Smith is still working on fixing now that we can re-produce the error locally.

• We’ve learned a lot about what kind of test coverage we have for JS in edx-platform

Removing edx specific packages

• Aximprovements is likely to start on this work post redwood cut.

  • specifically, packages packages where the code is in the edx github org

  • axim will open these may-june, but won’t merge without coordinating with 2u

    • 2u is likely swamped may-june with edx-platform observability switchover

Spreading out the release risk

• We have knowledge of what will be EOL, but we could be planning more with this knowledge

  • eg support windows sheet: https://docs.google.com/spreadsheets/d/11DheEtMDGrbA9hsUvZ2SEd4Cc8CaC4mAfoV8SVaLBGI/edit#gid=195838733

    • Felipe: Should we track React on this ?

      • Yes!

      • also: django-rest-framework

  • spreading out upgrades instead of cramming them in before the cut

  • no objections to the idea

• Some upgrades end up being dragged out, but then a deadline is what makes them speed up. There are often many upgrades in flight at the same time.

  • JR recommends focusing on one effort at a time

  • Py3.11 has been moving quickly in the past few months, with a lot of focus and intentionality, which is good

    • We made tickets in all the relevant repos

    • it’s good to know all the outstanding upgrades, but it’s also good to know which are higher priority. So, balance between parallelization and focus.

    • having one ticket with one assignee has helped the py311 upgrade move.

    • open to feedback on improvements on this process

• Leaders in upgrades

  • It helps to have someone leading an upgrade, coordinating the tickets across repos and rallying maintainers (eg Feanil 3.11, Felipe 3.12?!?)

  • Also helpful for this person to collect info – breaking changes and the like

  • thoughts on electing leads for upgrades?

    • Split the responsibility so that more people can take smaller roles in an upgrade.

• Feanil is writing down some process docs for upgrades. Would be good to get instructions for upgrades all types of repos. Just a lot of little steps to remember – udpdate the version, tag a release, update the constraint, yada yada

• What’s one we could start early?

  • Py3.12!

• Repo tooling modernization and consistency

  • setup.py → pyproject.toml and the like

  • should we have an example?

    • yes → the cookiecutter

    • but we need to get maintainers to update existing tools

  • could backstage help?

    • yes, we could be making UI elements showing the “health” of the repository

    • if you want to make backstage better, chat with Feanil, he’s happy to get you up to speed