Not at Motorola, but another company in the space.
Software upgrades were extremely methodical in nature. The change control calls had dozens of people on them, and the upgrade document was hundreds of pages long. The ops team (which was not the dev team) rehearsed the upgrade in lower environments for weeks before doing it for real. I was on upgrade calls mostly just as a security blanket in case developer intervention was required.
I feel bad for the folks who have to deal with the FCC paperwork. You never wanted to get invited to one of those calls, it was like having the Inquisition show up at your doorstep.
> How buggy software came to be installed on a running system is not yet known.
It may not even have been the software. Well, it might have been, but it might also not have been. I got paged out at 2am one time because the domain controller, which I do not own, rotated all the passwords for the managed service accounts, which I do not control, and the SQL database, which I do not manage, suddenly lost its shit and wouldn't let any apps log in. It fixed itself in about 15 minutes, but the state noticed, and we were doing paperwork for about a week after that.