Everything within this section is only visible while editing. Use Page Properties ID "STUB", "REFACTURE", "PROGRESS", "rDEV", "rDOC", "rLANG" and "DONE". Everything contained within the table is displayed in the (INTERNAL) Reports page.
Resources & Remarks
Modification History Add a new line to this table and fill it whenever you edit the page.
|
Looking for new features? Here, you will find what's new in a fresh yuuvis® version, as well as the rare cases - Breaking Changes - that might require your action when updating. |
yuuvis® Momentum is released in a release train strategy, with one release per quarter. The releases are labelled with a year and season, e.g., 2023 Spring, 2023 Summer, 2023 Autumn etc. In the regular maintenance package, a one-year long-term support (LTS) release is included.
Every Winter release will always be treated as a regular LTS release and will be maintained for the duration of one year and one quarter, until the next Winter release is available, which then supersedes the previous LTS release. There are no further features added in an LTS version during the maintenance period. For example, 2022 Winter will be the regular LTS version, and will be supported for an additional quarter after 2023 Winter is released, which is until 2024 Spring. During this time, new features will be made available in releases 2023 Spring, 2023 Summer, 2023 Autumn and ultimately 2024 Winter which will then become the new regular LTS release.
All releases between two Winter releases (Spring, Summer and Autumn) will supersede each other sequentially in the order of their release. For example, release 2023 Spring will be maintained until release 2023 Summer (three months). After 2023 Summer is released, 2023 Spring will not be maintained anymore, and all fixes will be available in the 2023 Summer version only.
Update is possible and guaranteed:
We make no further statements about version compatibility of different releases. We expect furthermore that releases are installed completely and do not allow mixing of components from different releases. The individual components within a release will respect and follow the semantic versioning, where major component version denotes API breaking changes.