Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
78:manageprocessversions [2022/01/14 20:50] – aakr | 78:manageprocessversions [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 29: | Line 29: | ||
===== Managing Working and Valid process versions ===== | ===== Managing Working and Valid process versions ===== | ||
- | It is highly recommended to **not set working version as valid**. | + | It is highly recommended to **not set working version as valid **// |
When a new process is created in an empty workspace, only working version would exist which would have become valid version by default. However, to avoid working version from been marked as valid for a new process, Stages automatically creates an additional empty valid version “V0”. Moreover, end users will now see the empty valid version instead of the unreleased working version, until a new valid version is officially released. This prevents modelers from accidentially revealing information that should not be shown to end users yet. | When a new process is created in an empty workspace, only working version would exist which would have become valid version by default. However, to avoid working version from been marked as valid for a new process, Stages automatically creates an additional empty valid version “V0”. Moreover, end users will now see the empty valid version instead of the unreleased working version, until a new valid version is officially released. This prevents modelers from accidentially revealing information that should not be shown to end users yet. | ||
Line 41: | Line 41: | ||
If the valid working version is selected, it will be treated like all other versions, e.g. modeling is not possible. When process interfaces are followed to other workspaces, the interface will point to the valid version of the other workspace. If the non-valid working version is being selected, the interfaces will point to the working versions of the other workspaces. | If the valid working version is selected, it will be treated like all other versions, e.g. modeling is not possible. When process interfaces are followed to other workspaces, the interface will point to the valid version of the other workspace. If the non-valid working version is being selected, the interfaces will point to the working versions of the other workspaces. | ||
+ | ===== Versioning of reference models ===== | ||
+ | |||
+ | Reference models like Automotive SPICE should **__not be versioned__** | ||
===== Import versions or translations ===== | ===== Import versions or translations ===== | ||