Time | Item | Presenter | Notes |
---|
| Edx-platform Node JS Upgrade | | "webpack v4 and selenium webdriver dependency. BOM tried to do this work, but has stopped doing it after running into dependency upgrade blockers (selenium driver issues and underscore tests).” Blocked by https://github.com/openedx/wg-frontend/issues/26 edx-analytics-dashboard repos are not yet upgraded, being worked by the 2U owning team.
|
| Previous Todos Updates | | 2U to update catalog-info.yaml file in the next few days for the things that they will maintain. This will also come with updated team names. Feanil Patel to follow up with Awais Q about python 3.12 PRs and whether they have been created or not across the org. Kyle to have more info on the libsass upgrade soon. Feanil Patel to follow-up about Node upgrade tickets with Adolfo
|
| | Feanil Patel | BTR will find bugs during a release but what are the expectations of the maintainers? Redwood Release Testing Strategy (Draft) What do we do when a release critical bug is found very late in the release process, do we keep the existing triage SLA or can we accelerate it during the late stages of the release. Note For BTR: Bugs from releases should be reported as issues on the relevant repo for maintainers to be able to see them.
|
| Forums Testing Help
| Feanil Patel
| |
Anchor |
---|
| repo-maintainers |
---|
| repo-maintainers |
---|
|
| Repo Interest and Catalog | | |
| Tutor Master Releases | Robert Raposa | Has there been any conversation about a live master release of tutor that we have running to find issues more quickly? |
| edx-platform Maintenance Discussion | | libsass - Kyle to come back with more info next week. Mongo Upgrade Testing - We should update the container for the hosted runner to have both versions of Mongo and then pick a different one during testing. This is the arbi-bom recommendation. Need to do the Mongo 5 upgrade, can’t just skip to 6 Docs said this is required so we have to incrementally run through all of this. Upgrade Version Path To upgrade an existing MongoDB deployment to 6.0, you must be running a 5.0-series release. To upgrade from a version earlier than the 5.0-series, you must successively upgrade major releases until you have upgraded to 5.0-series. For example, if you are running a 4.4-series, you must upgrade first to 5.0 before you can upgrade to 6.0. https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/ Open question: Can we have Tutor run through all the version upgrades or can we only go to Mongo 5 as a part of redwood. It might not make sense to do this in terms of capacity since there are a bunch of other things we want to upgrade.
Chintan was able to run Mongo 7 with edx-platform and cs_comment_service for a client without any issue.
Devstack - Interest in taking over devstack and do 2U specific things.
|