I don't think it is quite that simple. I would still expect a Jira issue to be created. Some projects use ReviewBoard or other tools and require a code review (those are mostly RTC projects). So just because Git helps with part of the problem it doesn't mean you don't have to become familiar with the project's mode of operation. That said, Git does make distributed development quite a bit easier.
Ralph On Oct 7, 2013, at 7:14 PM, James Ring <s...@jdns.org> wrote: > Whatever workflow we came up with, if we moved to Git I'd like to see > Gerritt (https://code.google.com/p/gerrit/) used for code review. > > On Mon, Oct 7, 2013 at 7:10 PM, James Carman <ja...@carmanconsulting.com> > wrote: >> All, >> >> If we did want to move to Git, we'd probably have to figure out how >> we'd manage our "workflow" (couldn't think of a better word). I >> suppose we'd have a separate repo for each component? What about >> proper vs. sandbox? How would we accommodate that paradigm? Has >> anyone else already gone through this thought process? I must admit, >> my git fu isn't what it should be. >> >> James >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
