Does anyone have any recommendations on how to manage multiple versions of a module?
For example, once a custom campaign is live, I'm sure the developers will want to keep at least two versions - the live campaign, and the next release.
We'd like to be able to do this during development, too, in order to try out experimental stuff safely.
Problem is, you can't have two resources with the same name in the same toolset data base.
So, should we make two toolset data bases? If so, how? Is there a better way?
Of course, it's possible to achieve version control within a single module instance - for example, by checking in the live campaign before working on the next release - but I'm looking for something more robust.
Managing multiple versions of a module
Débuté par
Proleric
, févr. 17 2010 03:09
Retour en haut
