Set up an instance hierarchy that best supports your development life
cycle.
This example demonstrates how to set up an instance hierarchy where several peer
sub-development instances have the same parent development instance, but a more
complex configuration may be required to handle multiple project teams or other
customer requirements.
Do not use Team Development with production or test instances.
- Do not use a test or production instance as the parent instance in Team
Development.
- Do not make any instance the parent of a production instance.
- Production instances should never have a parent.
When you back out a change on a Team Development instance, it backs out the
change all the way back down the chain, including undoing the work on the source
instance. This behavior can cause major problems on test and production
instances.
