This document covers SEP release versions and the terminology associated with these releases.

List of versions#

LTS and STS releases#

SEP is available and maintained in long-term support (LTS) and short-term support (STS) releases. The following processes around Trino open source releases and SEP releases, availability and support apply.


  • All Trino open source releases use an integer number such as 338.

  • An SEP release is created for each Trino open source release. It uses the source of the open source release, and adds the extensions and plugins.

  • Every release of SEP is created as an STS release first.

  • All STS releases use the Trino number with an appended -e, such as 338-e.

  • Some STS releases are promoted to LTS.

  • All LTS releases append a patch number, such as 338-e.0, 338-e.1, 338-e.2, and so forth.

  • LTS and STS releases include all release artifacts such as a tar.gz archive, an 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. As an alternative, you can change to use an STS version with the new feature and keep updating with each STS release until an LTS version becomes available.

STS releases#

  • Supported for use in production until the next STS release becomes available

  • Available shortly after each Trino 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#

  • Supported for use in production for 12 months

  • Only available for selected Trino 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:

LTS and STS support#

Release type

Supply patch releases for critical issues for

Provide support for


12 months

12 months


no patches, next STS provides fix

latest STS release only

Feature release status#

By default, features in SEP are released in a “general availability” (GA) state and are therefore considered to be complete and fully documented. Some features may be released in other status, and are documented as such in the reference documentation and product as needed.

The following table describes SEP feature release status and product expectations:

Feature release states#

Feature status



Limited preview

Early feature testing, limited to a select group of users giving active feedback. Not supported for production environments.


Public preview

Early access feature release, available for all users but not supported for production environments.

Partial or complete

Production availability

Feature is in active development but released for use in production environments. May have limited use cases or known limitations until GA release.


General availability

Feature is launched and stable for production with no major issues. Most SEP features are in the GA state unless documented otherwise.


All releases#

The following tables contains a list of all SEP versions, detailing LTS/STS qualifier, release date, and end of support date for LTS releases.

Starburst Enterprise LTS versions#


Release month

End of support

380-e.x LTS

May 2022

May 31, 2023

370-e.x LTS

February 2022

February 28, 2023

364-e.x LTS

November 2021

November 30, 2022

360-e.x LTS

August 2021

August 31, 2022

356-e.x LTS

May 2021

May 31, 2022

350-e.x LTS

March 2021

March 31, 2022

345-e.x LTS

November 2020

November 30, 2021

338-e.x LTS

July 2020

July 31, 2021

332-e.x LTS

April 2020

April 30, 2021

323-e.x LTS

October 2019

October 31, 2020

312-e.x LTS

June 2019

June 30, 2020

302-e.x LTS

March 2019

March 31, 2020

All older releases have reached their end of support date.

Starburst Enterprise STS versions#


Release month

End of support

379-e STS

May 2022

380-e LTS release

378-e STS </378-e/>

May 2022

379-e STS release

377-e STS

April 2022

378-e STS release

376-e STS

April 2022

377-e STS release

375-e STS

April 2022

376-e STS release

374-e STS

March 2022

375-e STS release

373-e STS

March 2022

374-e STS release

372-e STS

March 2022

373-e STS release

371-e STS

February 2022

372-e STS release

369-e STS

February 2022

370-e LTS release

368-e STS

January 2022

369-e STS release

367-e STS

December 2021

368-e STS release

365-e STS

November 2021

367-e STS release

363-e STS

October 2021

364-e LTS release

361-e STS

September 2021

363-e STS release

359-e STS

June 2021

360-e LTS release

358-e STS

June 2021

359-e STS release

357-e STS

May 2021

358-e STS release

355-e STS

April 2021

356-e LTS release

354-e STS

March 2021

356-e LTS release

348-e STS

December 2020

350-e STS release

347-e STS

December 2020

348-e STS release

346-e STS

November 2020

347-e STS release

344-e STS

September 2020

345-e LTS release

343-e STS

September 2020

346-e STS release

341-e STS

September 2020

343-e STS release

340-e STS

August 2020

341-e STS release

339-e STS

July 2020

340-e STS release

338-e STS

July 2020

338-e LTS release

336-e STS

June 2020

338-e release

334-e STS

June 2020

336-e release