As a team should we develop locally and merge into the dev server, or develop on the dev server?

Posted by CogitoErgoSum on Stack Overflow See other posts from Stack Overflow or by CogitoErgoSum
Published on 2010-03-23T20:50:49Z Indexed on 2010/03/23 20:53 UTC
Read the original article Hit count: 225

Hey, Recently I was tasked with writing up formal procedures for a team based development enviroment. We have several projects with multiple modules each. Right now there are only two programmers, however there are plans to expand to 4-6 programmers. Each programmer will be working on the same project and possibly pages which may cause over writing or error issues.

So far the ideal solution I have thought up is:

  1. Local development (WAMP/VM or some virtual server instance on their own machine). Once a developer has finished their developments, they check it into the CVS Repository and merge it wih other fixes etc.
  2. The CVS version is then deployed to the primary dev server for testing by the devs.
  3. The MySQL DAtabases are kept on the primary dev server and users may remotely connect to it. Any Schema / Data alterations are run through a DB Admin who will notify all devs of any DB Changes (Which should be rare).

Does anyone see an issue with this or have a better solution?

© Stack Overflow or respective owner

Related posts about development-environment