Building off of @Manu’s point, if we’re talking hotfixes/patches, what about a model where there’s ~10 developers that have the privilege to review and approve a hotfix/patch, and that only a certain fraction of them need to respond in order to push out the change? Maybe there’s some sort of Pagerduty integration for these chosen few.
Btw, how is the DFINITY neuron currently managed for pushing out hotfixes? What happens when it’s the middle of the night in Switzerland and an on-call alert goes off that requires an immediate patch fix? A developer submits a code change proposal, but then does someone wake up the person (or people) in charge of the DFINITY neuron?
I can’t imagine that Dom or Jan are the ones pressing the accept/reject button on all of these proposals.