Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.1] Redirect to current version of Release Support Timeline #10165

Closed
wants to merge 1 commit into from
+2 −73
Closed

[4.1] Redirect to current version of Release Support Timeline #10165

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 2 additions & 73 deletions about/release_policy.rst
View file
Original file line number Diff line number Diff line change
@@ -61,79 +61,8 @@ further developed for maintenance releases in a Git branch of the same name
Release support timeline
------------------------

Stable branches are supported *at least* until the next stable branch is
released and has received its first patch update. In practice, we support
stable branches on a *best effort* basis for as long as they have active users
who need maintenance updates.

Whenever a new major version is released, we make the previous stable branch a
long-term supported release, and do our best to provide fixes for issues
encountered by users of that branch who cannot port complex projects to the new
major version. This was the case for the 2.1 branch, and is the case for the
3.6 branch.

In a given minor release series, only the latest patch release receives support.
If you experience an issue using an older patch release, please upgrade to the
latest patch release of that series and test again before reporting an issue
on GitHub.

+--------------+----------------------+--------------------------------------------------------------------------+
| **Version** | **Release date** | **Support level** |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 4.2 | November 2023 | |unstable| *Development.* Receives new features, usability and |
| (`master`) | (estimate) | performance improvements, as well as bug fixes, while under development. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 4.1 | July 2023 | |supported| Receives fixes for bugs and security issues, as well as |
| | | patches that enable platform support. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 4.0 | March 2023 | |supported| Receives fixes for bugs and security issues, as well as |
| | | patches that enable platform support. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.6 | Q3 2023 (estimate) | |supported| *Beta.* Receives new features, usability and performance |
| (`3.x`, LTS) | | improvements, as well as bug fixes, while under development. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.5 | August 2022 | |supported| Receives fixes for bugs and security issues, as well as |
| | | patches that enable platform support. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.4 | November 2021 | |eol| No longer supported, as fully superseded by the compatible 3.5 |
| | | release (last update: 3.4.5). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.3 | April 2021 | |eol| No longer supported, as fully superseded by the compatible 3.4 |
| | | release (last update: 3.3.4). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.2 | January 2020 | |eol| No longer supported (last update: 3.2.3). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.1 | March 2019 | |eol| No longer supported (last update: 3.1.2). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 3.0 | January 2018 | |eol| No longer supported (last update: 3.0.6). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 2.1 | July 2016 | |eol| No longer supported (last update: 2.1.6). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 2.0 | February 2016 | |eol| No longer supported (last update: 2.0.4.1). |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 1.1 | May 2015 | |eol| No longer supported. |
+--------------+----------------------+--------------------------------------------------------------------------+
| Godot 1.0 | December 2014 | |eol| No longer supported. |
+--------------+----------------------+--------------------------------------------------------------------------+

.. |supported| image:: img/supported.png
.. |partial| image:: img/partial.png
.. |eol| image:: img/eol.png
.. |unstable| image:: img/unstable.png

**Legend:**
|supported| Full support –
|partial| Partial support –
|eol| No support (end of life) –
|unstable| Development version

Pre-release Godot versions aren't intended to be used in production and are
provided for testing purposes only.

.. seealso::

See :ref:`doc_upgrading_to_godot_4` for instructions on migrating a project
from Godot 3.x to 4.x.
For the a timeline of released versions and the current support status of each,
see the `up-to-date version of this page <https://docs.godotengine.org/en/stable/about/release_policy.html>`_.

.. _doc_release_policy_which_version_should_i_use: