Revision as of 23:16, 20 March 2006
Drupal is managed in Subversion on GMC. We've made modifications to the Drupal code and we want to keep them through upgrades, so when a new version of Drupal is released we want to make sure that we have a controlled upgrade process. The way we do this is by maintaining a vendor branch for the code from Drupal, and a trunk branch that contains the version of Drupal we're using with our modifications. When a new release of Drupal comes out, we commit that to the vendor branch, then use subversion to merge it into the trunk code. All of this is done on the staging server -- once that works properly we commit the changes to subversion, go to the production server and update it from subversion.
Because this is a public wiki, I've used fake paths.
Here are the steps:
- cd /var/www/test.gallery2.org/vendor
- wget http://drupal.org/files/projects/drupal-4.#.#.tar.gz
- tar --strip-components=1 -xzf drupal-4.#.#.tar.gz --strip-components=1 removes the first directory from all paths. now use use "svn st" and "svn diff" to assure yourself that everything looks ok
- svn commit -m "Update to Drupal 4.#.#" svn returns "YYY" as the change list id at this point the vendor branch is up to date. Now we can begin merging
- cd /var/www/test.gallery2.org
- svn merge -rXXX:YYY vendor trunk where XXX == YYY - 1. This merges all Drupal changes into our trunk it probably generates some conflicts. For each conflict, edit the file, resolve the conflict (they are often just changed numbers in $Id$ tags) and then do "svn resolved" on each conflicted file.
- svn diff Take a look at the diffs and make sure they look as expected. Test the dev site to make sure that the code around these diffs is ok.
- svn commit -m "Update to Drupal 4.#.#" Now the dev site is up to date
- cd /var/www/gallery.menalto.com
- svn up Now the live site is up to date.