But I can’t find information about the maintainer status of this, or if it’s still useful with how we manage code drift and release branches now? Do we still use it? What role/ticket is responsible with reviewing/merging the PRs?
@maxim do we want to update this to add our common ulmo branch of openedx-platform?
cc @Agrendalath as I see you’ve merged some of the sync PRs in the past.
@samuel, we never formalized this process. IIRC, we discussed passing this responsibility to the FFs, but I suppose we forgot to follow up. I used to merge these PRs when I had a moment, but then I had to work on older releases for a while, so I no longer had time and context to test the new ones. Also, resolving some of these merge conflicts became tricky over time, as we accumulated significant code drift.
I suppose it would be easier if we added Ulmo and removed everything else from there. Still, it would be nice to ensure somebody checks these PRs.
Still, it would be nice to ensure somebody checks these PRs.
Agreed! I wonder if this would be worth adding to some particular role. Perhaps to the community liaison, or at least to the community liaison to delegate? I’m easing into that role, and I see all these PRs now as I regularly check and keep tabs on everything.
I feel like to help deal with these kind of PRs, we need:
a quick way to determine which account we can log time to (it will be cumbersome to create a new ticket and discuss accounts for each new dependency update or code sync PR).
a quick way to find someone to delegate addressing it to.
If we have these, it would be easy for someone like the community liaison to eg. ping the FFs with “this Renovate PR just opened, please check and log time to BB-XXX”.