[support] Best version control practices

[Ari Davidow]

On Fri, May 28, 2010 at 4:52 AM, Rolf Kutz <rk at vzsze.de> wrote:
> On 27/05/10 16:38 -0400, Ari Davidow wrote:
>>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?
>
> I found this guide very helpful.
>
> http://nvie.com/git-model
>
> regards
> Rolf

Yes, that is a beautiful explanation of git. I am still trying to
think about the best way to deal with drupal configuration issues, to
note module dependencies, and to deal with the fact that in a cms
database, because of all of the auto-numbering dependencies, we have a
model where we have successfully merged content and code--exactly
where we didn't mean to be ;-). This may all clarify as I move
forward.

ari