...

A fundamental idea behind this strategy is that the owner and reviewers must have a shared model of how the code is changing, the bugs that are being fixed and who is making changes.  Neither the owner nor the reviewer should be surprised but a code change.

In summary, during normal development, an owner can change code at will and does not require a pre-commit code review or even a JIRA to track trivial changes.  Of course, code cannot be committed during a code freeze or ramp down without authorization and almost all work should have a JIRA to track it.  Owners are seasoned developers who know that even a trivial change can cause significant hardship so they are naturally cautious and understand when a "trivial" change is not trivial and requires a JIRA and a code review.

Technical Discussions and Code Reviews

...