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.
spreading out upgrades instead of cramming them in before the cut
no objections to the idea
Some upgrades end up being dragged out, but then a deadline is what makes them speed up. There are often many upgrades in flight at the same time.
JR recommends focusing on one effort at a time
Py3.11 has been moving quickly in the past few months, with a lot of focus and intentionality, which is good
We made tickets in all the relevant repos
it’s good to know all the outstanding upgrades, but it’s also good to know which are higher priority. So, balance between parallelization and focus.
having one ticket with one assignee has helped the py311 upgrade move.
open to feedback on improvements on this process
Leaders in upgrades
It helps to have someone leading an upgrade, coordinating the tickets across repos and rallying maintainers (eg Feanil 3.11, Felipe 3.12?!?)
Also helpful for this person to collect info – breaking changes and the like
thoughts on electing leads for upgrades?
Split the responsibility so that more people can take smaller roles in an upgrade.
Feanil is writing down some process docs for upgrades. Would be good to get instructions for upgrades all types of repos. Just a lot of little steps to remember – udpdate the version, tag a release, update the constraint, yada yada
What’s one we could start early?
Py3.12!
Repo tooling modernization and consistency
setup.py → pyproject.toml and the like
should we have an example?
yes → the cookiecutter
but we need to get maintainers to update existing tools
could backstage help?
yes, we could be making UI elements showing the “health” of the repository
if you want to make backstage better, chat with Feanil, he’s happy to get you up to speed