Page History

...

• push a tag for this release to git
• do a backup of the staging db (with the staging site offline)
• update the staging server's clone of your git repo
• check out all the stuff from the local git repo to a revision directory on staging
• change the 'current' symbolic link to point to the public directory inside new revision directory
• update symbolic links from the revision directory's public/sites/default/files
• put the site offline
• update the site's public, private, and temp files paths
• run update.php
• revert any features
• put the site back online

Server Directory

Note: We currently don't have the servers set up to follow Capistrano's 'current' symlink. To work things out I've added a 'cap' directory:
/libweb/sites/<domain name>/cap
and deployed the sites there. If you add a symlink like this
/libweb/sites/<domain name>/htdocs/capcurrent -> ../cap/current/public
you can see the deployed site at
http://<domain name>/capcurrent
BUT it only works if you turn off Clean URLS
http://<domain name>/capcurrent/?q=admin/config/search/clean-urls

Here is a JIRA issue about setting up new development and deploy servers.