Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

All public Working Group meetings follow the Recording Policy for Open edX Meetings

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

Previous TODOs

DescriptionAssigneeTask appears on
  • Jeremy Ristau Talk to Diana about helping coordinate the django upgrade.
Jeremy Ristau2024-09-19 Meeting notes
  • Feanil Patel Drop in #ask-2u about the potential index changes with the next Django update so Ristau can connect us with SRE
Feanil Patel2024-09-19 Meeting notes
  • Next time: Discuss access for teams that maintain many repos across the org.
 2024-09-19 Meeting notes
  • Next Time: Continued discussion on whether we should change the Depr 6-month window approach. Should we have one big ticket for something like Python 3.8 or Node 18 and just start the 6-month clock once all the maintained repos have been updated?
 2024-09-12 Meeting notes
  • Feanil Patel ticket enabling cron CI of master every week so we know when external changes might have broken some repos that are usually not getting updates.
Feanil Patel2024-09-12 Meeting notes
  • Brian Smith will update the DEPR pilot issue with the exception for unmaintained repos. Something like “Once all maintained repos have dropped support for something (post 6-month window), it is fair game to drop support in any unmaintained repo.” but with examples of when this notification happens.
Brian Smith2024-09-12 Meeting notes
  • Next time: 6-month support window for simultaneous python versions doesn’t seem prudent
2024-09-05 Meeting notes
2024-09-05 Meeting notes
  • Kyle McCormick Next time: Py 3.13 or Py 3.12 for next upgrade? Take a look at the changelog.
Kyle McCormick2024-09-05 Meeting notes
  • Jeremy Ristau ensure DEPR tickets are created for any frontend that can be deleted as a result of the new course-authoring MFE.
Jeremy Ristau2024-05-30 Meeting notes
  • Chintan Joshi Update maintenance docs with guidance for when to merge regular dependency update PRs
Chintan Joshi2024-05-23 Meeting notes

\uD83D\uDDE3 Discussion topics

Item

Presenter

Notes

Previous TODOs

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

✅ Action items

⏺️ Recording and Transcript

  • No labels