Posted on 2004-09-21
I have been put in charge of coming up with a plan for checkin/checkout.
This isn't as straight-forward as it seems.
There are 3 developers, including me.
We have a production server and a test server.
So I'm thinking of TURNING OFF the check in / check out feature on the production server. The reason being: We should have a policy that all development is done on the test server, and after the change has been made, it is copied to the production server.
Since no development is done on the production server, there's no need to check anything out.
Is that wrong?
Now onto the test server.... The test server is refreshed periodically from the production machine. That way we have a mirror image of the production box. If Chris is in the process of changing something, then when he comes into the office in the morning, he should sync his local with the remote.
The bottom line is this: I'm thinking of turning off "check out/in" for the test system as well!
If Chris and Jim are clobbering each other on the test system, then no harm done - that's a management problem to begin with - two people working on the same web page. I'm only worried about them clobbering each other on the production server.
If we only had 1 production server, I can understand the need for check out/in. But we have a production server and a test server.
Here is my question:
What's the best practice for team development in Dreamweaver, limited to making sure person A doesn't overwrite person B's changes.