15. Versions#
This documentation covers a number of Starburst products around Presto. Products follow different release cycles and version numbering schemes. Some restrictions exist around combining different versions and ideally you use versions that are designed to be combined and are all documented together here.
15.1. List of versions#
Starburst Enterprise Presto 332-e.9 LTS (release notes)
based on Presto 332 (release notes)
including the CLI, the Web UI, and the JDBC driver
Mission Control 0.23 (release notes, documentation)
ODBC driver (documentation)
presto-admin 2.10 (release notes, documentation)
AWS CFT/AMI 332-e.9-aws-ami-0.121 and 332-e.9-ami-0.121 (release notes, documentation))
Kubernetes resources 332-e.9-k8s-0.51 (release notes, documentation)
15.2. LTS and STS#
Starburst Enterprise Presto (SEP) is available and maintained in long-term support (LTS) and short-term support (STS) releases. The following processes around Presto open source releases and SEP releases, availability and support apply.
General#
A SEP release is created for each Presto open source release.
The release version number of SEP is identical to the Presto open source version with a
-e
appended. For example, the open source release 334 is used to create the SEP release 334-e by adding the extensions and plugins.Every release of SEP is assigned LTS or STS status.
LTS and STS releases include all release artifacts such as
tar.gz
archive,rpm
archive, container images, and additional tooling such as Kubernetes and CFT-related resources.New features are never backported, but only become available in newer releases. As a result LTS users, who want to stay with LTS versions only, need to wait until the next LTS release is available, to gain access to new features. Alternatively you can change to use an STS version with the new feature and keep updating with each STS release until an LTS version is released.
STS releases#
Support for usage in production until the next STS release becomes available
Available shortly after each Presto open source release of the same version
No issues in the release are fixed as patches to that release, any changes or fixes are incorporated in the next release. For example, a problem in 333-e is fixed and made available in 334-e, 335-e, or whenever a fix is available.
LTS releases#
Support for usage in production for 12 months
Only available for selected Presto open source releases
Limited, low number of release per year, at most one release per quarter
Some issues are backported to the release and made available as patch releases. For example, a problem in 332-e.2 is fixed and released in 332-e.3
The following resolutions for issues are backported:
Critical security fixes
Select fixes for critical defects that affect production usage, and for which no workaround is available. This may include incorrect results, severe performance regressions, and stability issues. The decision to backport such fixes is made by Starburst in collaboration with affected customers, if necessary.
LTS and STS support#
The following table shows the how long from the release date critical patches and support are provided:
Release type |
Supply patch releases for critical issues for |
Provide support for |
LTS |
12 months |
12 months |
STS |
no patches, next STS provides fix |
latest STS release only |
15.3. All releases#
The following table contains a list of all SEP versions, detailing LTS/STS qualifier, release date, and end of support date for LTS releases.
Version |
Release |
End of support |
June 2020 |
335-e release |
|
April 2020 |
April 2021 |
|
October 2019 |
October 2020 |
|
June 2019 |
June 2020 |
|
March 2019 |
March 2020 |
All older releases reached their end of support date.