SaaS CMS has officially launched! Learn more now.

Per Ivansson
Apr 12, 2011
  4261
(0 votes)

EPiServer Release Cycle Terminology

This post aims to clarify the terminology used for different stages in the release cycle of EPiServer products, the purpose and what can be expected in terms of feature completeness, upgrade paths and support. It also aims to answer the question : “What can I start to develop on?”.

CTP (Community Technology Preview)

A CTP release is the first stage of the release cycle with the main purpose to get early. CTPs releases can either be closed and targeted to a selected focus group or open to the public. CTP releases are not feature complete, has no supported, or even guaranteed possible,  upgrade paths to RTM. We strongly advice against using CTP releases as a starting point for projects aiming for production.

Beta

A Beta release is the second stage of the release cycle and the main purpose is still to get feedback on functionality but also to receive bug reports. Beta releases can be open or closed. Beta releases may not be feature complete but should have the main features in place. We generally describe breaking changes and upgrade paths to RTM but upgrade paths to RTM are not supported. Using Beta releases in projects aiming for production is not recommended but can at your own responsibility be a starting point for your project as the changes are often minor and in most cases documented to enable a manual upgrade to RTM.

RC (Release Candidate)

A RC release is the third stage of the release cycle and is generally feature complete and the main purpose is to get late feedback and bug reports. RC releases can be open or closed. No breaking changes are expected at this stage and upgrade paths to RTM are described and in most cases automated. RC releases and upgrade paths are however not supported and using RC releases in projects aiming for production is still on your own responsibility but upgrade to RTM should be fairly straightforward even though it might involve manual steps.

RTM (Release to Marketing)

A RTM release is the finalized product with full support.

GA (General Available)

GA is the publically available RTM release.

Note: Any intermediate builds between Beta to RC or RC to RTM, no matter how they are obtained, are not supported and have no supported or documented upgrade paths to RTM.

Apr 12, 2011

Comments

Please login to comment.
Latest blogs
Optimizely SaaS CMS Concepts and Terminologies

Whether you're a new user of Optimizely CMS or a veteran who have been through the evolution of it, the SaaS CMS is bringing some new concepts and...

Patrick Lam | Jul 15, 2024

How to have a link plugin with extra link id attribute in TinyMce

Introduce Optimizely CMS Editing is using TinyMce for editing rich-text content. We need to use this control a lot in CMS site for kind of WYSWYG...

Binh Nguyen Thi | Jul 13, 2024

Create your first demo site with Optimizely SaaS/Visual Builder

Hello everyone, We are very excited about the launch of our SaaS CMS and the new Visual Builder that comes with it. Since it is the first time you'...

Patrick Lam | Jul 11, 2024

Integrate a CMP workflow step with CMS

As you might know Optimizely has an integration where you can create and edit pages in the CMS directly from the CMP. One of the benefits of this i...

Marcus Hoffmann | Jul 10, 2024

GetNextSegment with empty Remaining causing fuzzes

Optimizely CMS offers you to create partial routers. This concept allows you display content differently depending on the routed content in the URL...

David Drouin-Prince | Jul 8, 2024 | Syndicated blog

Product Listing Page - using Graph

Optimizely Graph makes it possible to query your data in an advanced way, by using GraphQL. Querying data, using facets and search phrases, is very...

Jonas Bergqvist | Jul 5, 2024