The Life of a Patch program is in fact a way of showing how a patch is evolving from the moment it is written and until it is executed. The author of the patch, of the code that is going to be used by many, many others after him, is setting up the local environment where he will develop the apps or the app, if it is about a single app, and he uses the tools Git and Repo. Then, he gets the codes that are already written by others (so, in a way, he already benefits of some advantages), and transfers the codes from the public depot to his own environment.
The author may simply develop the codes, based on the codes that he has transferred earlier, but this is not so extraordinary, so he better uses the codes and create new ones. Anyway, after he decides what to do, he develops the code as he wants and changes the files of an old application or of a new one, just to see if the new code is working properly. Attention: this does not mean that the new app is tested, only the code is. When the code is ready, the author submits the changes that he has done to the Gerrit system. This system notifies the verifiers that they have work to do regarding your project. Also, it notifies the project owners or verifiers.
The approver looks at the code and takes the decision if it is good for this new project that the author is planning to make. If it is, then he accepts the change, if not the project is sent back for further development. If the “code looks good”, it is approved and sent to Gerrit, where the code is tested again and again to see if it works in different environments. The code returns in a way back to the verifier and he submits the change made by the author. Gerrit takes the new code and adds it to the public depot, where the rest of the developers can benefit of it.11