2024-09-19 Meeting notes

Python 3.12 vs 3.13

• Python API doesn’t have a lot of significant changes.

• C API has a lot of changes

• 30% of packages currently support 3.13 explicitly

• 3.11 is supported until 2027

• Right now we have a mix of 3.11 and 3.12, it would be good to get to 3.12 for everything then take a break.

• What would we do instead of Python upgrades?

  • Node Upgrade

    • Let our dependencies dictate what version we jump to.

    • This becomes simpler as frontend-base become more standard.

• Proposal: Finish the 3.12 upgrade, skip 3.13

  • Focus on

    • Django and Node updates

    • setup.py replacement

Appropriate length of DEPR window

• …Continuing discussion from last time…

  • DEPR Process Vision

    • Propose which things get the new version and old version at the same time.

    • Once we have completed the addition of the new version. We announce that the timer has started for dropping support.

    • Any work done before the date of support drop, still has to support both versions.

    • Once the drop date has been reached, any repos that still only run the old version can be updated without needing to support both versions for a given release.

• New question that arose since last week: we have toggle dates in the code. Can we use those, particularly when the replacement is at full parity?Re: MFE Rewrite Tracker | Comment

BOM team Repo access

@Jeremy Ristau

• Arbi-BOM team needs to be able take action on many repos to be able to do maintenance and can’t currently new employees can’t merge things.

• What are they doing that needs direct write access to all the repos?

  • Landing Upgrade PRs across many teams.

    • Python update PRs

    • Node update PRs

  • There is a middle ground of something like the frontend-all style team.

    • Can we do something like that for other groups?

  • Can we have a core-maintainers team that any org can put resources into that would be able to merge?

  • Can we have some people with merge writes?

    • There is also an on-call rotation which is tricky.
      
      

Check on cookie-policy-banner enzyme replacement

@Glib Glugovskiy

Released in v2.6.0, can be closed

frontend-app-payment Node 20

@Brian Smith

• https://openedx.slack.com/archives/C04BM6YC7A6/p1726236856476109

• Node 20 upgrade · Issue #858 · openedx-unsupported/frontend-app-payment

•  

edx-platform discussions below Here

Django Upgrade

• The index changes are gonna impact us in edx-platform the most probably.