[support] Best version control practices

Ari Davidow aridavidow at gmail.com
Thu May 27 20:38:41 UTC 2010


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


More information about the support mailing list