RU 🇷🇺
...
| Table of Contents | ||||
|---|---|---|---|---|
|
The Hub allows users to download, install, and run every version that’s been released to their company. Multiple versions can be installed at the same time, and users can choose which version they wish to run. This empowers users to select which version they want to run, and are not forced to immediately upgrade when new features are released.
...
A build of the software has a version number, which looks something like 1922.23.253. In this example, 1922.2 3 is the major version, and 253 is the build number.
The major version looks something like 1922.5 2 or 2022.1 3 or 2023.31. The 19 22 or 20 23 represents the year in which the version was released, and number after the “.” increments with each new major version released over the year.
The build number increments each time Alastri creates a new build. The build number increments globally across all versions, so it’s possible build 450 is for version 2023.1, while build 451 is for version 1922.43. Essentially the build number is a unique id of the build.
...
Each major version is associated with one of four release types. These are based upon the level of testing that has gone into them, their purpose, and whether they continue to be supported with new releases for bug fixes.
Release Type | Description |
|---|---|
Legacy | An old release with Alastri is not actively supporting. Bug fixes are only available in emergency situations, and no further enhancements will be made. If a bug is encountered, the first suggestion from Alastri will be to update to a Current version. |
Current | A recent release which Alastri is actively supporting. Very minor enhancements may be added in rare circumstances. Alastri recommends users stay on these versions, unless there is a compelling reason not to be (such as requiring brand new functionality only available in an Experimental release). |
Experimental | A very recent release which Alastri is actively supporting. These releases are continually updated with new functions and features. There is a higher likelihood of bugs in these versions than in Current versions. We recommend you use these builds only if you require a new feature that is not in Current. |
Explosive | A development release which Alastri is not actively supporting and should be used for testing purposes only. These versions are not typically visible. |
Release Schedule
Alastri releases a new build usually several times a week. A build is a specific version of the software which can be downloaded, installed, and run. There are two main reasons for a new build to be released:
...
Upgrading from the major version to a later build of the same major version will almost always not require any changes on your part. As an example, you can open version 1822.43.242 and upgrade to 1822.43.278, and this will likely not require any changes on your part. When changes are required, it is because there was a bug which requires minor alterations to the model setup. As an example, there might be a bug which allowed the user to set up the model in an invalid way, and once that bug is fixed, the user will be required to fix the setup.
...
| Info |
|---|
Upgrades are One-Way While you can upgrade a model from an old version to a new version, it is not possible to open a model saved in a newer version in an old version of the software. Therefore, before upgrading it’s it is recommended to save a backup. |
...
Alastri’s products are built to work together, but this is only possible if they’re all of the same version. Therefore, when upgrading one product to a specific version, you must upgrade the others to also be on the same version, if you wish to use them together. For example, if you upgrade RR to 2022.2.152 and you want to use the output with APS, you need to upgrade HI to 2022.2.152 and APS to 2022.2.152. Then, if you want to use the output from APS with SC, then that will need to be on 2022.2.152 as well.
An outcome of the above is that you should also work on the same version as the others you are working with, so the team as a whole needs to choose a specific version to work with.
...
If you’re halfway through a plan: stick to the same major version unless there is an issue preventing you from proceeding.
If you work at a company which has a central point of contact with Alastri: refer to that contact who will tell you which version to use.
If you’re on a Legacy release: Upgrade to a Current release when you’ve got a chance.
If you’re looking to get access to the latest and greatest features, and are not up against a planning deadline: Use an Experimental release.
Do not use an Explosive Release, unless specifically instructed by Alastri.
| Tip |
|---|
If you’re still not sure which version to use, select the latest Current releaseselect the latest Current release so that if you do require assistance from Alastri, we can help. |