FLEXSCHE Version Upgrade Policy
Here, we will provide a detailed guide on the version upgrade policy for FLEXSCHE products (hereinafter simply referred to as FLEXSCHE).
The version number of FLEXSCHE is
represented as such. If the major version is 17, the minor version is 1, and the revision number is 12, the version number notation will be
17.1.12
.
The major version is updated approximately once a year. The minor version at the time of a major version upgrade is always 0, and it increases sequentially to 1, 2, ... with subsequent minor version upgrades. However, it is also possible to skip minor version upgrades and proceed to the next major version upgrade. After a major version upgrade, an announcement is made on each mailing list, along with an introduction of new features added since the last major version upgrade.posted on this website.
During a major version upgrade, the maximum usable version of licenses with maintenance contracts is updated. By accessing our server using the License Key Updater (a tool included with FLEXSCHE) and reflecting this update information on your license key, you will be able to use the latest major version.
If a bug is found in a released "Maintenance Supported" version, a revised version will be released irregularly. In this case, the revision number is not necessarily sequential and generally increases like 4, 7, 8, 10, ... The initial revision number at the time of a version upgrade is indefinite.
Only the latest revisions of the following three versions of FLEXSCHE are subject to maintenance (i.e.,Supported OSoperation is confirmed and guaranteed on licenses with maintenance contracts).
- "Latest Version"
- "Previous Version" (the version immediately before the latest version)
- "Maintenance Supported Old Version" (the last minor version of the major version before the previous version)
Versions that do not fall into these categories are "Non-Maintenance Supported Versions," but you can continue to use them as long as there are no operational issues.
For example, if the released version is
... / 15.0 / 15.1 / 16.0 / 16.1 / 16.2 / 17.0
and the "Latest Version" is 17.0, the "Previous Version" is 16.2. The "Major Version before the Previous Version" is 15, and its last minor version is 15.1, so the three maintenance-supported versions are
15.1 / 16.2 / 17.0
. After 17.1 is released, 15.1 will be removed from maintenance support, and
16.2 / 17.0 / 17.1
will become the new maintenance-supported version.
If a bug is found in a maintenance-supported version, a revised version will be released as needed. The timing of the release of the revised version depends on the importance of the fixed bug. If all are minor, the guideline is once every 1-2 months, but if a major bug is included, it may be released as soon as the fix is completed.
For the supported OS of each version,please check the Supported OS list.
Note that the version upgrade policy for FLEXSCHE CarryOut is different from this, but there is a dependency with the FLEXSCHE products introduced here, so it is not completely independent.
FLEXSCHE projects (data) are basically upward compatible, and past version data can be loaded and operated correctly in the new version, developed with careful attention. However, it is not entirely impossible for behavior to change. Therefore, in each user's version upgrade work, operation confirmation and verification are necessary, and it is not uncommon for version upgrade work to be postponed even when a new version is released. Even in such cases, this version upgrade policy is adopted so that you can continue to use the old version with peace of mind.
* The version upgrade history exemplified on this page is fictional and does not match the actual version numbers released in the past.