Page Comparison

Share Maintenance Prioritization Sheet

Feanil Patel

• https://docs.google.com/spreadsheets/d/1rMwbRldYwp-xPsAG2vijqwB__9M7P2AgjDxX31G7ucA/edit#gid=0

• Another element of the maintenance work

  • System Level Dependencies

• Piotr - Opencraft is doing doing some testing with mongo 7.2

  • 5.x release added some backwards compatability layer and OC has not run into any issues with running 7.0

• edx-platform test infrastructure currently run by 2U, Ristau to find out how we can test on newer mongo versions.

Review Current and Upcoming Major Upgrade Tasks

Feanil Patel

• Useful Link: https://docs.google.com/spreadsheets/d/11DheEtMDGrbA9hsUvZ2SEd4Cc8CaC4mAfoV8SVaLBGI/edit#gid=195838733

• Django 4.2 - Just merged in edx-platform the last repo that needed it.

  • ecommerce/ecommerce-worker are still on Django 3.2

    • PRs are ready for testing but we need some people test.

      • https://github.com/openedx/ecommerce/pull/4073/files

  • If we can’t find help to test, we may accelerate deprecation.

    • https://github.com/openedx/edx-platform/pull/34156

• Python 3.8 → 3.11/3.12

  • Some discover started at 2U, no detailed review of this work yet.

  • Needs more discovery.

    • Maybe target both 3.11 and 3.12 for testing.

• Node JS Upgrade

  • 7 left on Node 16

  • Node 18 support being dropped for some 3rd paryt packages we rely on already.

• Ruby

• Mongo

• Ubuntu

• Elasticsearch

  • Lower priority for now.

  • Some discovery work is attached as PDFs in https://github.com/orgs/openedx/projects/9/views/4?filterQuery=-deprecation-ticket-type%3A%22Supporting+Deprecation+Work%22++elas&pane=issue&itemId=2303649
    

CC requirement for new repos that need maintenance

Felipe Montoya

• To be a maintainer, you need to be a CC for a repo, it’s hard to do that with smaller low use repos or repos where devs can’t get PRs reviewed.

  • Can we fast track or change this process in some way?

  • Can we say that anything that doesn’t have a maintainer can be requested by anyone that is is a core contributor?

  • Can we do this more easily for repos that have not been touched in a long time?

  • Nominating existing CCs or other engineers with existing orgs even if they don’t have experienece in those repositories.

    • Concern, existing CCs should not lower the bar for CCs that are taking on maintenance.

• Where will the new maintainers info be documented?

  • Backstage / catalog-info.yaml file should be the source of truth.

  • The repo priorities spreadsheet will also have a new column that has this info to ease the burden on Contribution Coordinators

  • What can we do for review today? It’s unclear who the reviewers are at 2U or which teams that still exist.

What Is 2U Still Maintaining

• Axim will review and audit with 2U the existing maintained repos and make sure we are still aligned.