Skip to main content

​
Extended Maintenance release

Extended Maintenance (EM) releases provide you with a long-term support Prophecy version, along with the following benefits:
  • Upgraded third party libraries for robust security posture
  • Full performance and scale testing to check resource guidance
  • Direct upgrade path from a previous EM release to the next one
  • One year of technical support and hotfixes for critical issues
You can expect a new Extended Maintenance release two to six weeks after each Major release.

​
Required resources

Starting with v3.4.1.0 EM, SQL Sandbox is enabled, so every SQL pipeline session will spin up an additional pod with the following configuration:
  • CPU: 500m
  • Memory: 512Mi
After upgrading to 3.4.1, you must enable SQL Sandbox Config in the UI by navigating to the Sandbox Config tab in the Config sub tab of the Admin Settings. "sqlSandboxPoolSize" must be set to a minimum of 2. This parameter determines the number of pods that are kept in a ready state. You will need additional SQL Sandbox resources for each simultaneous user session.

​
Prophecy support lifecycles

The following table describes the support stages for Prophecy versions. Prophecy supports GA versions for six months, unless the version is an Extended Maintenance (EM) release, which Prophecy supports for one year. For information on supported Prophecy versions, see Version Chart. Workloads on unsupported Prophecy versions may continue to run, but Prophecy doesn’t provide support or fixes.

​
Prophecy version lifecycle

PhaseDescription
GA, full support for Extended Maintenance releasesCritical stability and security fixes are backported only for EM releases.
End of supportIf a version is unsupported, then workloads running on these versions receive no Prophecy support.
End of LifeProphecy reserves the right to completely remove a release version at any time after support ends.