Here’s a general walk-through of the code submission process, for those who are curious:
- The coder works on a “working” or “feature” branch, based on the master branch of Review Board.
- The coder makes sure to update their master branch, and merge with their working branch to make sure they don’t get “bit-rotted” (their code becomes conflicted with the current state of the master branch)
- When the fix is finally done, the coder uses the post-review tool to create and post a patch up to http://reviews.reviewboard.org for review.
- The coder is now responsible for making sure someone reviews that patch. This might involve some gentle prodding / reminding.
- Once the patch receives a “Ship-it” from one or more mentors, one of those mentors will take the patch and push it to the Review Board master branch, with the coder’s name as the author.
And that’s it – that’s how a patch gets submitted.