CET 12.0 Major Release Timeline

Not sure how to start migrating? Refer to our Migration: A Complete Guide articles.

Questions? Contact Developer Support. devsupport@configura.com

Infographic

Text-Based

Period	Date	Event	Details
Beta	29 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. Beta Download Link Briefcase Announcement
	9 April	Migration Guide	A guideline on what code in CET's core has been added, changed, or removed. Migration Guide from 11.5 to 12.0 CET 12.0 QA Testing Guide
	12 April	Migration Webinar	A webinar on what has been added, changed, or removed in CET's code core. Developer Migration Webinar: - Briefcase announcement - YouTube video QA Migration Webinar: - Briefcase announcement - YouTube video
RC	19 April	RC Release Day	Release Candidates are Beta build versions with the potential to be the final released product on release day. RC Download Link CET Pre-Release Notes Link Catalogue Tools Pre-Release Notes Link
	19 April	Pre-Release Notes Announcement
	3 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.
	10 May	Release Dates Announcement	You can find the list of Extension's planned release dates for the 12.0 update here.
Official	17 May	Official Release Day	Configura expects partners to release their extensions during the 2-week extension release window. If you do not release your extension on time, it will block users from updating to the latest version of the software, creating an undesirable experience for everyone involved. CET Release Notes Link Catalogue Tools Release Notes Link
		Release Notes Announcement
		Release Window Opens
	31 May	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.

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.

What Tests Should I Do?

Smoke
Regression
Migration

Are There Any Guides I Can Refer To?

Articles in this section