27 May
2010
27 May
'10
8:38 p.m.
So, there you are. You have your production site in Drupal. You have the database tables and code stored in the version control software of choice (cvs, svn, git, mercurial, whatever).
But, of course, you are constantly developing new modules, testing new configurations, etc. on your dev site.
1. What processes have worked for capturing versioning info in your version control software? 2. What processes have worked to support sane workflow from qa or dev to production? 2a. How on earth do you sanely capture configuration data for each module?
ari