Skip to content

Instantly share code, notes, and snippets.

@dwoz

dwoz/00065-lts-releases.md

Created April 20, 2022 21:22
Show Gist options
  • Save dwoz/40045cd780b154e9238318e9a107b8c6 to your computer and use it in GitHub Desktop.
Save dwoz/40045cd780b154e9238318e9a107b8c6 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
00065-lts-releases.md
  • Start Date: 2022-04-20
  • SEP Status: Draft
  • SEP PR: (leave this empty)
  • Salt Issue: (leave this empty)

Summary

The core team would like to move to an LTS release strategy

Motivation

Our curret release strategy causes us to provide security and bugfixes for as many as five versions. Our documented life cycle has become less sustainable as we've increased the frequency of releasing new versions of Salt.

Design

We would like to move to maintaining at most two branches/versions of Salt. We can accomplish this by designating a single version as Long Term Support (LTS). A LTS version would be supported with bugfixes and security fixes for a longer period of time than our current life cycle allows. I propose a 2 year LTS window.

Alternatives

Change the current life cycle to provide support for less versions and/or for a shorter durration per version.

Unresolved questions

  • One big question is how long does an LTS version remain supported? I propose a 2 year support cycle but I could see a case made for 3 years.

  • At what point do we stop supporting OSes that have reached end-of-life status for the LTS version?

Drawbacks

I think the core team all agrees this is the best path forward. I'm looking forward to hearing what drawbacks the broader community can come up with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment