Skip to content

Commit

Permalink
Merge pull request #480 from humanmade/backport-476-to-v14-branch
Browse files Browse the repository at this point in the history
[Backport v14-branch] Update the LTS page with latest release information
  • Loading branch information
mikelittle authored Mar 23, 2023
2 parents 0f01ba1 + 02704bb commit 1685184
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions other-docs/guides/long-term-support.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,20 @@

# Long Term Support

To provide stability to Altis users, major Altis releases will be supported for a minimum of one year after their release. The latest release of Altis will receive full support, while older releases will receive support under the "long-term support" policy.
To provide stability to Altis users, major Altis releases will be supported for a minimum of one year after their release. The latest release of Altis will receive full support, while older releases will receive support under the ["long-term support" policy](#long-term-support-policy).

[Learn more about how Altis releases work here](./altis-releases.md).

At all times, only a single major Altis version is fully supported, and is the "active" release. When a new major version of Altis is published, the previously active release moves into long-term support mode.

For example, if Altis has quarterly releases (i.e. four releases per year), each release will be the "latest" for 3 months, and will be supported under the long-term support policy for a further 9 months:

![Long term support timeline diagram](./assets/long-term-support.png)
<figure>
<img src="./assets/long-term-support.png" alt="Diagram showing overlapping releases and their support timelines">
<figcaption align="center"><b>This diagram illustrates the overlapping support timelines for releases</b></figcaption>
</figure>

For the current releases see the [releases page](docs:/releases)

## Long-term support policy

Expand Down

0 comments on commit 1685184

Please sign in to comment.