Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/content/en-US/docs/1.getting-started/3.releases.md
blob: 0d64d61a76463ca065a176619772e301dd3d1ef1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
---
title: Releases and support
description: How Tazel is numbered, and how long Rolling, LTS and ELTS releases are supported.
---

<!-- SPDX-FileCopyrightText: 2026 Progmasoft <support@progmasoft.com> -->
<!-- SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Grant-1.1 -->

A version of Tazel has four numbers: `MAJOR.SEMIMAJOR.MINOR.PATCH`, such as `0.4.0.3`. Every release has a tag
`tazel-<version>` and release notes on [GitHub](https://github.com/Progmasoft/tazel/releases).

## Three kinds of release

| Kind | Supported for | Which releases |
| --- | --- | --- |
| Rolling | 6 months | every release that is not LTS or ELTS, and every release before `1.0.0.0` |
| LTS (Long-Term Support) | 5 years | the line `A.0` of each `MAJOR` from `1.0.0.0` on |
| ELTS (Extended Long-Term Support) | 12 years | the LTS line of `MAJOR` 1, 4, 7 and every third after them |

The time counts from the first release of the line. A supported line receives fixes for bugs and for security
problems as new `MINOR` and `PATCH` releases; it receives no new features, which come in the Rolling releases.

## Which one to use

- **Rolling** brings each feature first. Take the newest release; the one before it stays supported for 6 months.
- **LTS** stays on one line for 5 years, for projects that upgrade once in a while.
- **ELTS** stays on one line for 12 years, for products that ship Tala programs for a long time.

Every release of Tazel before `1.0.0.0` is Rolling.