user: release: LTS support

This commit is contained in:
Earl Warren 2024-03-23 07:24:44 +01:00 committed by Earl Warren
parent 3693fe0926
commit 73e569c299
4 changed files with 57 additions and 8 deletions

View file

@ -3,6 +3,11 @@ title: 'Installation'
license: 'CC-BY-SA-4.0'
---
Forgejo publishes a stable release every three months and a long term
support (LTS) release every year. Patch releases are published more
frequently and provide fixes for bugs and security
vulnerabilities. See also how [the Forgejo versioning scheme](../../user/versions) works.
This guide covers the installation of Forgejo [with
Docker](../installation-docker/) or [from
binary](../installation-binary/). Both of these methods are created

View file

@ -1,18 +1,17 @@
---
title: 'Upgrade guide'
license: 'CC-BY-SA-4.0'
origin_url: 'https://forgejo.gna.org/Hostea/admin-guide/src/branch/master/README.md'
---
This guide helps Forgejo admins perform upgrades safely and provides guidance to troubleshoot problems. It also covers upgrades from Gitea back to version 1.2.0.
## Release life cycle
Each Forgejo version undergoes the following states:
Each Forgejo release undergoes the following states:
- **Experimental** (current development version): receives new features, should not be used in production
- **Stable** (latest major version): receives full support, bugfixes and security fixes
- **Old Stable** (previous major version): receives only critical security support
- **Stable** (latest release): receives full support, bugfixes and security fixes for three months.
- **Long term support (LTS)** (the version published the first quarter of every year): receives only critical bugfixes and security support for one year.
- **Experimental** (current development version): receives new features, should not be used in production.
To be notified in advance of security releases, watch or subscribe to the RSS feed of the [security-announcements repository](https://codeberg.org/forgejo/security-announcements/issues). The details of the vulnerability will not be revealed, only the expected release date, for administrators to plan ahead and better secure their instance.