@Rocky what is StarRocks release schedule? What release will be LTS next?

The StarRocks release schedule and Long-Term Support (LTS) policy follow a predictable pattern focused on maintaining a balance between new features and production stability. Release Schedule * Minor Versions: A new minor version (e.g., 3.4, 3.5, 4.0) is released approximately every four months. These typically occur in the Jan/Feb, May/June, and Sep/Oct windows. * Patch Versions: Maintenance patch versions (e.g., 3.3.x) are released every 2–3 weeks to address bug fixes and security vulnerabilities. * Maintenance Window: StarRocks officially maintains the three latest minor versions. Given the four-month release cycle, a minor version is generally supported for approximately one year. LTS and Stable Versions StarRocks periodically designates specific minor versions for long-term support to provide a more stable foundation for production environments. * Current LTS/Stable: * Version 3.3 was officially designated as an LTS version in mid-2024. * Version 3.5 is currently tagged as the "Stable" release in official documentation (as of June 2026). It is the recommended version for users prioritizing stability over the cutting-edge features of the 4.x branch. * Next LTS: * While the 4.x branch is the current "Latest" line (with v4.1.1 released in May 2026), the community has not yet explicitly named the next specific 4.x version that will receive the formal LTS badge. * Based on historical patterns (LTS versions like 2.5, 3.3, and the stable status of 3.5), an LTS designation is typically given to versions that have reached a high level of maturity after a major architecture shift (like the v4.0 release). Summary for Planning: If you require long-term stability today, v3.5 (Stable) or v3.3 (LTS) are the recommended paths. If you need the latest features like improved JSON performance or enhanced Iceberg integration, the 4.x branch is the active development line. References • developers/versions.md • introduction/maturity.md • introduction/versioning.md • release_notes/release-3.4.md • release_notes/release-3.2.md

@Rocky so as of now starrocks maintains 3 branches 3.5.x 4.0.x 4.1.x and once 4.2 will be released 3.5.x will go out of support?

The StarRocks maintenance policy is based on the "three latest minor versions" rule, which aligns with your observation, though the transition is defined by specific states (Bugfix-only vs. Code-freeze). Maintenance Lifecycle According to the official Version Release Guide, StarRocks maintains the three latest minor versions. The status of a version changes as new ones are released: 1. Latest Version (e.g., 4.1.x): Enters

feature-freeze

upon release (only enhancements and bugfixes). 2. Previous Version (e.g., 4.0.x): Becomes

bugfix-only

(no enhancements, only bugfixes). 3. Third Oldest (e.g., 3.5.x): Remains

bugfix-only

. 4. Fourth Oldest: Enters

code-freeze

. In this state, no pull requests are merged except for critical CVE (security) fixes. To your specific question: Once v4.2 is released, the "three latest" will be 4.0, 4.1, and 4.2. At that point, v3.5.x will enter

code-freeze

. This is effectively the end of standard maintenance, as regular bugfixes will no longer be backported to that branch. ────────── LTS and "Stable" Designations StarRocks uses "LTS" and "Stable" labels to guide production users: * Current LTS: v3.3 was officially designated as an LTS version in mid-2024 to provide an extended maintenance window. * Current Stable: v3.5 is currently the designated "Stable" release (as of June 2026). It is the recommended version for users who prioritize stability over the newer features of the 4.x branch. * Next LTS: There is no official announcement yet for which 4.x version will be the next LTS. Historically, StarRocks designates an LTS version after a major architectural shift (like the jump to 4.0) has had time to mature. Given that 3.5 is "Stable," it is the closest current equivalent to a long-term branch until a 4.x version receives the formal LTS badge. Recommendation: If you are planning a production deployment today and want the longest support runway, v3.5 is the safest choice. If you need the 4.x features, be prepared to follow the upgrade path to 4.1 or 4.2 within the next 4–8 months to remain within the "three latest" support window. References • developers/versions.md • introduction/versioning.md • introduction/maturity.md • release_notes/release-4.0.md • release_notes/release-3.3.md References • developers/versions.md • introduction/maturity.md • introduction/versioning.md • release_notes/release-3.4.md • deployment/upgrade.md