ScreenConnect release process

I frequently receive questions regarding ScreenConnect releases, and I would like to provide insight into our process.

Our release process starts with internal builds in a non-production environment. Once our QA engineers have completed sanity checking we progress through the following stages for cloud production:

• Internal: At this stage, a new release build is branched/deployed to cloud staging. Our QA engineers conduct sanity checks to ensure operational integrity before advancing to the next phase.
• Canary: Publicly accessible builds are made available, and all instances on a FREE license type are updated. While paid partners have the option to update to this build, we generally advise against it because full regression testing has not been completed.
• Preview: Upon completion of regression testing and resolution of any identified bugs, we transition to the preview phase. Our goal is that the preview build represents code completion, so unless a critical defect is encountered, the Preview release will be simply promoted to the next phase with no changes.
• Stable: The stable phase is usually reached within a week of entering Preview. Our phased release approach involves initially upgrading a small percentage of instances to allow for thorough testing before gradually increasing the rollout. In case of a critical bug, the rollout is paused until a fix is implemented. The complete rollout typically takes around two weeks to reach 100%. It is important to note that manual upgrades can be performed at any time via the cloud portal.

For on-premise partners, the pre-release becomes available on our download page shortly after the cloud enters the Preview phase. The stable release for on-premise partners is released when the cloud rollout reaches 50% to ensure the absence of critical issues.

In all phases, we update our output stream so that our partners can follow along with the contents of the release: https://screenconnect.product.connectwise.com/communities/26-screenconnect-output-stream