saltstack / saltstack/salt-install-guide
[DOCS]: Clarify LTS release/promotion/schedule process
@scriptautomate-bc is already working on this.
Since Nov 10, 2025.
- Dominant language
- Python
- Stars
- 7
- Forks
- 13
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
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 when "CVE and critical support" ends or some combo thereof with Support Phases 1-3+Extended Life support)...?
Ultimately:
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.