Change Managment

[rodbell]

Hi Guys,

I was wondering if there are any good articles/posts on best practises for managing changes in a sugar installation.

I.e. Maintaining Dev, Test and Prod environments.
Applying patches and Updates
Moving customizations between them.

I have seen article where people have done this using SVN (or similar).
I am also wondering if people do it with Studio/Module builder?

Thanks,
Rod.

[andopes]

We use both Studio and SVN.
We implemented a tool called SVN tools, which automatically store all custom fields into a metadata file whenever a custom field is created, updated or deleted. This same SVN tool is able to also automatically install into current instance all custom fields committed into repository.
We play SVN for all projects of ours without big deal. We are able to manage all changes, create installers from specific revisions, update live system from tags etc.

Cheers