Page Comparison

...

\uD83D\uDDE3 Discussion topics

Item	Presenter	Notes
Previous TODOs		Ecommerce DEPR Ticket: https://github.com/openedx/public-engineering/issues/22 DEPR for forking Footer: https://github.com/openedx/frontend-component-footer/issues/459
DEPR tickets for upcoming upgrades	Kyle McCormick	is it appropriate at this point to make DEPR tickets for version of Node and Python that we’ll be moving on from soon? [DEPR] Node 18 support [DEPR] Python 3.11 support We’ll make the DEPRs once there is action that operators can take. I.e. There is a new version for them to move to that is tested and supported.
Roles and Permissions	Feanil Patel	Still in very early stages, once we have a suggestion of steps forward it will go through the normal product review process so keep a look out there.
py 3.13 instead of 3.12?		3.13 release is Oct 2024 https://devguide.python.org/versions/#supported-versions Concerned about our libraries having added support.
edx-platform specific maintenance
studio DEPRs		Hard to get this scheduled DEPRs do two things They tell people that a breaking change is happening They provide a place to collect feedback on the change

Next time: 6-month support window for simultaneous python versions doesn’t seem prudent
Kyle McCormick Next time: Py 3.13 or Py 3.12 for next upgrade? Take a look at the changelog.
Next Time: Teak Maintenance Goals, take a look at https://docs.google.com/spreadsheets/d/1wtpoypH1XOPc_G6h9AUNXJ6XiNKD6dlkMP3lubdpE9I/edit?gid=195838733#gid=195838733

...