Deployment Process - abought/osf.io GitHub Wiki

Overview

When a developer takes on one or more issues, they must fork the OSF repository to their own Github account. Each issue must be a separate branch, named referencing the issue - e.g., issue-88.

Once changes are ready for review and inclusion in to the production branch (master), the developer must submit a pull request to the staging branch of the COS repo.

The pull request will then be reviewed and (if accepted) merged it into the staging branch. The staging server will then be rebuilt using the testing default build, and automated testing will be initiated against it. Another developer (Melissa?) will then be notified of the deployment and will begin manually testing.

Once automated and manual testing is complete, an email will sent to the OSF-dev mailing list, notifying all members of the changes currently pending in the staging environment, and giving them a set period of time to go out and test them as they feel appropriate.

Finally, once this time period has passed and assuming no major issues are discovered, the changes will be merged into master, and the production server will be re-deployed to include them.

Tools

The staging server should be accessible at http://staging.openscienceframework.org/.