Required Releases
Allow releases to be marked as ‘required’ so that devices in a deployment are forced to update to specific versions before receiving the latest.
eg. A deployment has 3 releases in its history, v1, v2, and v3. If no releases are marked as ‘required’, v3 will be sent to devices, but if v2 is a ‘required’ release and there are devices still on v1 firmware, they will be requested to update to v2 first before then being asked to update to v3.
Status: Planned
Log in to comment and vote
No comments yet
Be the first to share your thoughts.