Web Cube Release Process

The following document will detail the release process for a Web Cube site. The document covers the qualifications for a significant (major/minor revision changes) and incremental release, as well as details the specific release and update process for significant release process per hosting tier.

Tier 1 Hosting

Web Cube Tier 1 Hosting has a streamlined release process, accounting for the site traffic, that maximizes procedure and diligence, while minimizing cost.

1. Confirmation of Changes on Development System

2. Update of Staging Site Codebase

3. Review of Staging Site Changes

4. Temporary Downtime to Update Live Codebase

5. Launch, Live Site Testing and Monitoring

Tier 2 Hosting

Web Cube Tier 2 Hosting has a thorough release process reflecting the uptime critical, high traffic nature of its hosting. The procedures are built to ensure maximal testing, review, and confirmation, and minimal downtime to secure changes and launch, followed with thorough monitoring.

1. Confirmation of Changes on Development System

   All changes and bug fixes are reviewed in the development environment to ensure that all requirements are met.

2. Run Automated Test Harness on Development System

   Core expected functionality is confirmed by running the test harness on the development system.

3. Update to Development Site

   All code on development system is checked in and the development site is updated to the latest revision.

4. Run of Automated Test Harness on Development Site

5. Sync of Live Data to Staging Site

6. Update of Staging Site Codebase

7. Run of Automated Test Harness on Staging Site

8. Run of Manual Test List on Staging Site

9. Downtime Scheduled for live site

10. Site Transfer

11. Live Site Testing and Monitoring

Enterprise Hosting

Web Cube Enterprise Hosting provides High Availability (HA) cluster management and a tiered release process with minimal or zero downtime if at all possible. HA clusters are specifically tuned with Web Cube per task, and a specific release process taking in to account the cluster composition will be created upon cluster setup.