One of the benefits of having a SaaS-based event technology platform is the fact that there are predictable releases, bringing our customers up-to-date technology with no installation needed. To help clarify the Certain release cycle, we have outlined the basic definitions, frequencies, and notification processes below.
A major release introduces a major functionality or enhancement. They are referred to as Certain20YYRX, where X is the number of major release for the year, R1 is the first major release of the year; R2 is the second major release of the year (example = Certain2012R1).
System availability: systems or services may be unavailable for up to 3 hours
Notification: Yes, 2 weeks in advance both on the product and Website.
Minor releases introduce minor functionality enhancements and/or defect fixes. They are referred to as Certain20YYRX.Y; where Y is the number of minor or “.dot” release (example = Certain2012R1.3)
System availability during release: No planned interruption of services (exceptions may apply)
Frequency: Every Month
Notification: 2 weeks in advance both on the product and Website
Patch releases introduce defect fixes. Denoted as Certain20YYRX.Y.Z, where Z is the number of patch release (example = Certain2012R1.3.4)
Notification: No notification necessary