On Wed, May 1, 2013 at 4:03 PM, Nathan England <[email protected]> wrote:
We really don't want to change our setup because of some rigid quality > control that > must be done, so that really is out of the question. How do we make git > work best > for our setup? > Do we really need to change? If you're not using revision control now, then, most emphatically, yes, you need to change. > Is there a better way for our review > process by the QA team? (who are *not* coders at all, btw) > > I would set up a ci server to build and deploy your applications. Then after the build on test is certified by QA, they promote it to production and maybe even deploy to production using the CI server. I would either use git tags or build artifact versions that can be used to determine a git hash to track exactly which code gets deployed to production. I don't see any reason git wouldn't work for you. You sound as if you have some reason to think it wouldn't, but don't say what it is. Barry /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
