OWB repository management

Question

OWB repository change management
I had created a OWB repository, owb_test, to develop & test modules defined for our warehouse. Hence, in owb_test may contain different types of modules where some of them are defined for testing purpose.
Do you recommend another OWB repository, eg owb_prod to keep those modules that actually being deployed to our warehouse production enviornment? Or should it be better to remain as one repository i.e owb_test, housekeep and change the module status from Development to Production?
Can anyone share with me on how you manage the OWB rep change control? Thanks

Answer 1

It depends on how strict you would like to do version control... but the most strict way to do it would be to create several repositories (or multiple projects in the same repository) and maintain version control and propagating changes through MDL export and import (in that respect, multiple repositories is easier to manage).
If you are less strict about version control or your environment is less complex, you can probably get away creating multiple projects (one for each environment) and copy/paste objects from dev to test, to QA, to prod. This scenario would also work if you create multiple modules (instead of multiple projects).
Hope this helps,
Mark.