Hi, On Wed, Jul 22, 2009 at 5:46 PM, Tekkub<[email protected]> wrote: > Peter, In that workflow, you have one person performing the merging, > staging, and testing. You can stage multiple times if you like, and "save" > those staged points in temporary branches. If you've got multiple repos > that need to be tested together, again, you have one person that's > coordinating all of that. Essentially, developers are assigned tasks by > this person, fix them in topic branches, push them, and pass things on to > the coordinator. The developers test locally during dev of course, but > never worry about the process of getting things tested for QA and deployed > to production. They simply branch off master because that's what is live, > and what needs fixed. So there effectively isn't a "freeze", the > coordinator just might not assign out or merge in feature branches.
Thanks. I do appreciate your comments. Some of this has more to do with how an organization operates than with Git per se. This particular workflow does not map well onto our organizational workflow, though it might work well for some. -P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
