Designer Release Versioning Conventions
The Designer release versioning policy was first introduced in r28 to provide clarity on how we iterate Designer releases.
The version naming convention for Designer is r'MAJOR'.'MINOR'.'HOTFIX'.
Version numbers are incremented based on the nature of the changes in each release:
-
MAJOR: Incremented when a release includes major changes that impact workflows, or where users must relearn how to perform existing tasks. A major release can also include support for, or deprecation of Disguise hardware products. -
MINOR: Incremented for feature additions and UI changes. -
HOTFIX: Incremented for patches and bug fixes that are backward compatible where you can revert a project file to an earlier hotfix version.
Release version naming conventions by change type
The table below shows different types of changes and indicates which types of release they can be found in:
| Change | Major | Minor | Hotfix |
|---|---|---|---|
| Requires a new OS for any Disguise Hardware product | ✔️ | ❌ | ❌ |
| Supports new Hardware product type | ✔️ | ❌ | ❌ |
| Modifies public API | ✔️ | ❌ | ❌ |
| Replaces an established workflow | ✔️ | ❌ | ❌ |
| Modifies the UI | ✔️ | ✔️ | ❌ |
| Adds new user-editable fields to objects | ✔️ | ✔️ | ❌ |
| Removes user-editable fields from objects | ✔️ | ✔️ | ❌ |
| Adds new features that benefit from (but do not require) a new OS on any Disguise Hardware product | ✔️ | ✔️ | ❌ |
| Adds new functionality to Designer | ✔️ | ✔️ | ❌ |
| UI changes | ✔️ | ✔️ | ❌ |
| Bug fixes | ✔️ | ✔️ | ✔️ |
For information about how to upgrade and downgrade your Designer project see our Upgrading and downgrading Designer projects page.