Team collaboration setup

[Joakim Karlsson]

We are trying to figure out the best way to configure EA database & VC to allow collaboration in a somewhat distributed team. I have read the whitepapers on deployment and version control, but there is so many options that we are having a hard time figuring out the best approach.

How have you configured your environment to allow easy collaboration and keeping a version history so that you may revert changes if so needed?

When you are working against a DB your changes are saved immediately. How can you keep two versions of the model to allow referencing the current project version while continue development on the next version? What we have experienced milestones doesn't work since a revert of a milestone resets the DB to that milestone. Anyone have any insight on how to work with several project versions (i.e. development, test, release)?

/Joakim

[Geert Bellekens]

Joakim,

Version control is all nice and dandy, and works reasonably well with EA, but please avoi about branching (e.g. multiple paralell versions) like the plague.
It's not the branching, but the merging that's going to be a killer.

EA v9 promises some improvement in this area, so wait and see.

Geert