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.
one big DEPR, and spin up smaller DEPRs for straggler repos?
Let’s do one for edx-platform, we can figure out the other things later when we have more info about them.
should we update .nvmrc now?
6 months from now, along with tutor
this is the “contract” portion
robert: I thought we thought we wouldn’t be able to support both
feanil: often is hard but it seems like we’re fine now
When does the timer for 6-month timer start?
Create a DEPR for Node 18 for edx-platform.
We need to have fully expanded by Sumac cut (Oct/Nov)
Contraction will happen in after 6 month timer, which is basically right after Node 18 support goes away
SWITCH to full Maintenance WG
Node 20 - Expand Contract
We’ll make a DEPR for edx-platfrom but probably just make one high-level OEP for all the other MFEs
Tracking DEPRs and other granular tickets
Should all DEPRs go on the maintenance board?
Does it make sense to just operate off the DEPR board and not have a maintenance board that’s meant to be publicly followed?
How can we plug into the existing communication channels rather than inventing new ones?
Maintenance board is for planning and high level view and the DEPR board is where you go to learn about changes that might break you or where code is going away.
Maintenance board is for planning and high level view and the DEPR board is where you go to learn about changes that might break you or where code is going away.