[LRUG] [Workflow] Getting a Pull Request from creation to merge

[Matthew Rudy Jacobs]

(This is a process question, rather than a Ruby question)

How do you folks manage getting code from pull request to production?

At Enthuse.me we work in the following way;

   1. we take a card
   2. we work on the code until we believe it is done
   3. we issue a pull request
   4. another member of the team takes a look at the pull request
   5. we converse about any issues
   6. we make any changes
   7. another member of the team merges the pull request
   8. the code is deployed to the QA server
   9. the product owner checks the function on QA
   10. the code is deployed to Production

This all seems to be fine,
but the problem is context switching.

Steps 4 to 8 can take a couple of days to run through.

Maybe I finish the code on Friday, but no one is free to review it until
Monday.
I start working on something else, then someone raises an issue with my PR.
When I'm next free I take a look, deal with their questions, make some
changes, and ask them to take a look again.

That process takes a lot of time, and requires both the reviewer and
myself, to switch back and forth.

How do you deal with this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20130819/3dca09cd/attachment-0003.html>