During Development
Check your code into ucsf/docroot/sites/dev.yoursite.ucsf.edu via Git
Code checked into the master branch is available within 5-10 minutes on development (i.e. http://dev.yoursite.ucsf.edu)
Moving Code to Staging and Production
- Check your code into ucsf/docroot/sites/yoursite.ucsf.edu via Git
- Your code will be tagged moved to staging in the next change control window
- Test your code change on stage before the next change control window
- The tagged code base will be migrated on the following change control day.

Example:
- Jane A. Dev checks her development code into ucsf/docroot/sites/jane.ucsf.edu on Monday 11/01/2011 at 2 pm,
- The code is migrated to staging on Monday (11/01/2011) afternoon.
- Migrating the code creates a "tag", a snapshot of that day's code
- The tag has a date in our example it would be tag/2011-11-01
- Jane tests stage.jane.ucsf.edu on Tuesday. Everything looks good.
- The code in tag/2011-11-01 is migrated to production Tuesday afternoon.
Second Example
- Jane A. Dev checks her development code into ucsf/docroot/sites/jane.ucsf.edu on Thursday 3/15/2012 before 4 pm.
- The code is migrated to staging on Thursday (3/15/2012) afternoon.
- Migrating the code creates a "tag", a snapshot of that day's code
- The tag has a date in our example it would be tag/2012-03-15
- Jane tests stage.jane.ucsf.edu on Friday. Everything looks good.
- The code in tag/2012-03-15 is migrated to production Monday afternoon.
What to do when something goes wrong on staging.
- Notify ITS
- Remove the problem code from Git
- ITS will notify the Drupal Users group and deploy a new tag to staging on your behalf.