Versioning
Contents
Overview
Test Methods and Products both have support for versioning. This means that any changes to them must be published before those changes can be used when creating new lifecycle data, such as samples and tests.
However, draft changes are immediately available to use when configuring setup data. For example, you do not need to publish a test method before it can be used to configure a product specification. For more information see Product Specifications.
Newly created data has an initial version of draft:0.1 .
Version Format
When configuring setup data such as products and test methods, the version number is shown in the top right of the screen.
The version tag will be in the format:
status:published-version.draft-version
- Status: Can be either 'Draft' or 'Published'. This indicates the current state of the data.
- Published version: This indicates the latest published version of the data. All data begins with a value of 0 [never published].
- Draft version: This indicates the latest draft version of the data. Each subsequent save to the data increments this number by 1. This resets back to 0 when the data is published.
Creating New Versions
To create a new version of data, simply press the [Save] button after making some changes. The version draft number will increment. For example, if your data has version draft:0.4 , it will subsequently change to draft:0.5 .
To create a new published version of data, simply press the [Publish] or [Save and Publish] buttons. The published number will increment by 1. For example, if your data has version draft:0.4 , it will subsequently change to published:1 .
Versions in the Lifecycle
During the lifecycle only published versions are available for use. Therefore, lifecycle data will only ever be shown to have a single version number (for example v1 ). This number represents the published version used. It is not currently possible to change the version of existing data within the lifecycle.