For example, it might take just "four lines of code" to change the Chrome's SSL padlock into a smiley face, but that would be a significant change, that would require hundreds of training docs' to be updated, and potentially re-training of end users.
More likely it's highly dependent on where that code is, your exact manager chain, etc. It could just as easily be that you picked the week a new manager started or a new process was put in place that turned out to be terrible and was so rolled back.
Absolutely. There are many good and valid reasons. The net result though is the same in terms of the impact to GP's personal productivity. People tolerate bureaucracy to different degrees, and it's a personal balance for everyone.
The six months of process was the minimum and all I wanted to change was a goto, eliminating a dead code branch. I can't even imagine if I had tried to make deeper changes.
Having said that, there have been times when I wished Google had a process that would keep some of their odder mistakes from happening. Most recently the android calendar client changes. No month view, really?
The amount of review you mentioned could be excessive or just the minimum because the entire product was sensitive or high risk. With no context it's hard for us to judge.