You need to sign in to do that
Don't have an account?
Best Practices: Collaborative development, version control and sandboxes
Hi All,
I'm looking at best practice suggestions for collaborative development in Force.com. I'm working on a project which is scaling up from a single developer to several.
Ideally I'd like us to work in seperate sandboxes, merge and deploy to a single pre-release sandbox, test, tag and deploy from there. I'm considering using version control on the IDE side and forcing state changes in the cloud through forced 'save to server's. Although this wouldn't covery object state and other metadata.
A couple of questions:
i) How do others handle collaboration and versioning?
ii) Can one version state of non-programmatic constructs (ie. custom objects, etc)?
iii) Is there someway of cloning the state of my sandbox directly into that of another developer?
Any thoughts/ suggestions/lesson-from-the-fieldwould be valuable.
Thanks,
raf