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 »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

⏪ Previous TODOs

DescriptionAssigneeTask appears on
  • Kyle McCormick will update the DEPR Pilot ticket with the new suggestion for planning major maintenance DEPRs
Kyle McCormick2024-09-26 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
  • 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

\uD83D\uDDE3 Discussion topics

Item

Presenter

Notes

Begin Recording


edx-platform Meeting


  • Which Repos need Python 3.11 Tests

  • All others repos will target 3.12.

  • Redwood cut is 1.5 months from now and we’re not seeing a lot of activity on

  • Chintan/Feanil will do an example upgrade and write up a wiki page for upgraders (of libraries, in particular).

    • Kyle will add help-wanted labels to small repos and send out a call for help.

    • Will 2u teams be able to help pile on these package upgrades?

      • → Jeremy will ping them

      • Feanil: Python upgrade is higher priority than React upgrade due to support windows

    • reminder: assign yourself (or use assign me command) as a way to say that you’re working on it

    • One item to add to that page: Pay attention whether it’s 3.12 optional, or 3.12 required, or 3.12 not possible (scipy/numpy dependencies)

  • Kyle McCormick will look at edx-sandbox / codejail-includes

    • lock current py38 requirements file and make a new one

    • to do: look into that and write up the plan

  • libsass update - on track to completion

  • OSPRs in edx-platform

    • What is the new escalation path?

      • Escalate to CCs instead of Arch-BOM

Python 3.11 Risk

Feanil Patel

  • Release is going to be cut Apr 28, wihch means we don’t have a lot of time to get changes landed. We need the work prioritized.

2U CCs Conversation Update

Feanil Patel

  • Gonna discuss with the TOC will have more updates soon.

Next steps for PR management

Tim Krones

  • 2 Questions about Automation

    • Are we ready to automate steps Michelle and Tim are doing?

      • Letting the PR authors know who they can reach-out to when items are ready for review.

      • We’re ready to update messaging for the openedx-webhooks bot

    • Who would handle that work? Does it need to be Axim.

      • No, we would appreciate contributors, but we could support

Maintenance tickets on open edx roadmap

Jeremy Ristau

Should top-level maintenance initiatives be on the Open edX Roadmap board?

  • Feanil: yes, I think so

✅ Action items

⤴ Decisions

  • No labels