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

Version 1 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
  • 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

Discuss access for teams that maintain many repos across the org

  • Introduction of a new CC Role for maintainer-at-large role

    • Will be posted to the forums shortly

    • We can follow up on discussion in that post for feedback.

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?


  • Proposal to shorten the DEPR simultaneous support window to 4-months, for future upgrade DEPRs that need to have a support window/operator impact.

    • We chose 6-months to guarantee it would be in one release.

  • Alternate Proposal:

    • Provide a predictable time when the fix will be gauranteed to be available within the next six months.

    • Announce the DEPR as early as possible (6-months is ideal) and at the end of the DEPR, there has to be a 1-month period of simultaneous support.

      • The Plan is announced early and the time when the work is completed is as predictable as possible.

      • If the work is done early, we should keep the original date but this could be negotiated. Get agreement from people running master.

      • If the work is completed late, we provide a 1-month simultaneous support window from the time of completion.

      • We give at least six months announcement window. But the work does not need to have started or completed when we make the announcement.

Teak Maintenance Goals, take a look at https://docs.google.com/spreadsheets/d/1wtpoypH1XOPc_G6h9AUNXJ6XiNKD6dlkMP3lubdpE9I/edit?gid=195838733#gid=195838733

Next time

edx-platform Specific Conversations

Celery sharing

Config overrides and YAML

✅ Action items

  • Kyle McCormick will update the DEPR Pilot ticket with the new suggestion for planning major maintenance DEPRs
  • Next time: Toggle annotations and DEPR
  •  

⤴ Decisions

  • No labels