...
Softrip releases new versions of its applications and components every three weeks (“Sprint”).
This three-week process is split up defined as follows:
Two weeks of development
Build a “Release Candidate” at the end of the two weeks of development
One week of Quality Assurance
Test and fix any gaps found in the Release Candidate
Promote the Release Candidate to Stable at the end of the QA week
New Stable version is available to be deployed to client Testing environments for User Acceptance Testing, or to client Production environments if UAT passes
Start the next 3-week Sprint
Example
Mon 01 May - Fri 12 May
Softrip implements scheduled fixes and features
Mon 15 May
Softrip builds a new Release Candidate for the new version
Mon 15 May - Fri 19 May
Softrip deploys and tests the Release Candidate in QA environments (daily deployments)
Any bugs or incomplete implementations found are addressed during this week and updated in the Release Candidate
Fri 19 May (EOD)
Softrip promotes the Release Candidate to Stable
Mon 22 May
Softrip deploys the new Stable version to client testing/UAT environments
Mon 22 May - Fri 26 May
Client tests the new Stable version in their Test environment and report any bugs found to Softrip
Softrip reviews reported bugs to be addressed as a hotfix (to be fixed in current version) or for a future Sprint/version
Mon 29 May
Softrip deploys the new Stable version to client Production environments
...