Unity Release Cadence and Process
The following documentation applies to customers on a Unity code version whether Upstream or Midstream.
Release Cadence
Product Manager will define the release scope with input from the Engineering team.
Monthly
Consolidated release including feature and bug stories.
Functionality that does not require re-implementation, significant setup changes, or changes existing customer workflow within the application.
As Needed Throughout the Month
Production patches for critical functionality that cannot be held until monthly release.
This will only cover critical issues and not be incremental bug fixes.
Quarterly?
Feature releases that include functionality that requires more intensive documentation and training or possible re-implementation.
Release Process and Timeline
Once the release is defined, the clients will be notified of the release and scope included. The dates around that process are outlined below.
23rd of each month - Clients are notified of a new release via the in-app notification system. The client will get the release notes for all items in the upcoming release including any critical patches done within the current month.
30th of each month - Release is pushed to client non-PROD environment.
10 days to identify blockers - Clients have 10 days to notify us of any critical fixes that would delay PROD deployment.
Any patches done during this period will be pushed to all client non-PROD environments to maintain consistency in version being tested.
~15th of each month - PROD deployment over the weekend that is immediately after or includes the 15th.
Risks & Open Items
Process and timing in Jira to release version to enable in-app release note functionality.
CloudOps needs to standardize naming convention of all Unity client non-PROD environments to be used for release testing. This will eliminate the need to track different non-PRODs for each client as the target for deployment.
What will be the timing to push patches during the 15 days of testing to all Unity clients to maintain a consistent version base?
PROD deployment over the weekend assumes no client process are being run during that period.
Currently, CloudOps can only check process and servers for processes running prior to deploy as a safety step. Ideally, our deploy tool should not allow a deploy when processes are active.
This is both a concern for us and for clients as several processes can leave data in a bad state if interrupted and it becomes a problem our team has to solve.
Example timeline of current release timing outlined in attached link.