The latest Release information is available below.
The T2S Release Concept is shown in the following table.
Q1
February | A “problem release” is planned for the third weekend in February. - This release delivers the resolution of reported problems in production.
- The concept defines a testing period of two weeks in UTEST, so that CSD participants can execute their test cases for the upcoming deployment.
|
Q2
June | A “major release” is planned for the second weekend of June. - This release will cover functional enhancements, meaning it will include T2S changes. It might deliver the resolution of reported problems in production.
- The concept defines a testing period of eight weeks in UTEST, so that CSD participants can execute their test cases for the upcoming deployment.
|
Q3
September | A “problem release” is planned for the third weekend in September. - This release delivers the resolution of reported problems in production.
- The concept defines a testing period of two weeks in UTEST, so that CSD participants can execute their test cases for the upcoming deployment.
|
Q4
November | A “minor release” is planned for the third weekend in November. - This release delivers the resolution of reported problems in production. It can potentially include functional enhancements if determined by the different T2S committees.
- The concept defines a testing period of four weeks in UTEST, so that CSD participants can execute their test cases for the upcoming deployment.
|
CEU implements CASCADE Releases along with the T2S June and November Releases.
