Release Channels #
Release channels let you deliver different versions to different license holders based on their track preference.
The Three Channels #
| Channel | Typical Audience |
|---|---|
| stable | All customers (production-ready releases only) |
| beta | Customers who want early access to new features before general release |
| alpha | Developers and testers evaluating pre-release builds |
Channel Hierarchy #
Each channel is a superset of the one below it:
alpha (sees: stable + beta + alpha versions)
beta (sees: stable + beta versions)
stable (sees: stable versions only)
A customer on the beta channel receives both beta and stable versions. They will update to the latest stable if it is newer than the latest beta, and to the latest beta if a newer beta exists.
What This Extension Adds #
Core DMSI-DDLS has a simple Beta checkbox on versions. With DMSI Update Server, each version is assigned one of three channels (stable, beta, alpha), and each license can be assigned a channel preference. The API only delivers versions the license is eligible for based on channel.
Setting a Version's Channel #
In the version edit form, under Update Server Settings, select the channel from the Release Channel dropdown. Default is stable.
Setting a License's Channel #
Channel is stored in license meta. You can set it:
- In the license edit screen (if core supports custom meta editing)
- Via customer portal: customers change their own preference in Notification Preferences
- Programmatically via the
dmsilm_us_license_channelfilter
The Default Channel for New Licenses #
New licenses default to the stable channel. Customers who want beta access must opt in via the portal or you must set it manually.