Infographic
Text-Based
| Period | Date | Event | Details |
| Beta | 20 March |
Beta Release Day | The Beta build is made available for testing. Configura starts doing regression testing during this period, so please migrate your extensions as soon as possible. Briefcase Announcement 14.0-BETA-64-BIT |
| Migration Guide | A guideline on what code in CET's core has been added, changed, or removed. Migration Guide |
||
| 22 March |
Migration Webinar |
A webinar on what has been added, changed, or removed in CET's code core. |
|
| 27 March — 17 April |
Migration Workshops |
Workshops to participate in to help guide on how to migrate in a much more interactive way. |
|
| RC |
17 April |
RC Release Day | Release Candidates are Beta build versions with the potential to be the final released product on release day. Briefcase Announcement 14.0-BETA-64-BIT Pre-Release Notes: CET 14.0 Major Pre-Release Notes: Catalogue Tools 14.0 Major Pre-Release Notes: Developer & QA Tools 14.0 Major |
| Pre-Release Notes Announcement | |||
| 1 May |
Release Sign-Off Deadline | To ensure a positive user experience with CET and its Extensions, an important step is for Manufacturers to migrate, test & sign-off on their Extensions before each release. Read more here. |
|
| 8 May |
Release Dates Announcement | You can find the list of Extension's planned release dates for the 14.0 update here soon :) |
|
| Official | 22 May |
Official Release Day |
Configura expects partners to release their extensions during the 3-week extension release window. |
| Release Notes Announcement | |||
| Release Window Opens | |||
| 5 June |
Release Window Closes |
Beta & RC Testing
Why Test in Beta?
Beta is a build that precedes RC. It requires testing after incorporating new features and fixes. Testing against Beta allows the team to identify issues in the core system and your extension. Raising concerns during this period gives Configura time to have them addressed.
You can further refer to the Migration: A Complete Guide help articles to guide you into placing your build into the Beta build for us to test earlier.
Why Test in RC?
Release Candidates are Beta build versions with the potential to be the final released product on release day. Testing against RC gives a first-hand experience of what to expect when running your extension on the released product.
You can further refer to the Migration: A Complete Guide help articles to guide you into placing your build into the RC build for us to test earlier.
Comments
0 comments
Please sign in to leave a comment.