Skip to content

[DOCS]: Clarify LTS release/promotion/schedule process #52

@mdschmitt

Description

@mdschmitt

Description of Issue

salt-version-support-lifecycle.rst has a lot of good info, but one thing that's a little unclear to me is how a new LTS is actually released (or "promoted"..?). Does the most recent STS just become the new LTS as soon as the current LTS reaches EOL (and if so, is it after "Active Support" ends or "CVE and critical support" or some combo thereof with Support Phases 1-3+Extended Life support)...?

What can/should users who currently run the LTS version do to prepare? Maybe more importantly, is there a notification blast somewhere that an upcoming LTS is being shipped beyond "new tag in GitHub, go for it"..? Currently the granularity is "November", and it was already bumped out from September (#48), what rationale or reasoning prompted that and where can I subscribe to such an info stream?

Version

3006, 3007

Operating System

N/A

Relevant log output

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions