Upgrading core for Drupal.org sites

Last updated December 19, 2012.

Drupal.org sites are branched from a Drupal core vendor branch:

• bzr+ssh://util.drupal.org/bzr/vendor/drupal/{6 or 7}
• bzr+ssh://util.drupal.org/bzr/vendor/pressflow/6.x-unbranded

1. Start with a checkout of your site from bzr+ssh://util.drupal.org/bzr/[site.]drupal.org
2. Preview updates
   bzr missing --theirs bzr+ssh://util.drupal.org/bzr/vendor/drupal/7, or another vendor branch.
   This should be a small number of updates; if it is many, you might have the wrong vendor branch.
3. Merge updates to your local checkout
   bzr merge bzr+ssh://util.drupal.org/bzr/vendor/drupal/7
4. Review, commit, test, and deploy.

Updating vendors

This only needs to happen once per Drupal core version. Double check the vendor branch before proceeding. Be sure to load every version once, in order; so everything is available to site maintainers.

If the core vendor branch is out of date, run update_vendor_branch in Jenkins with parameters

• PROJECT_SHORT_NAME: drupal (usual project short name)
• VERSION: 7.12 (usual full version number)

Pressflow

1. Go to a checkout of bzr+ssh://util.drupal.org/bzr/vendor/pressflow/6.x.
2. bzr import pressflow-6-….tar.gz downloaded from https://github.com/pressflow/6/tags, and commit.
3. Go to a checkout of bzr+ssh://util.drupal.org/bzr/vendor/pressflow/6.x-unbranded.
4. bzr merge bzr+ssh://util.drupal.org/bzr/vendor/pressflow/6.x, and commit.