Godot release policy¶
3.2 branch is no longer supported, and therefore its documentation
cannot be kept up-to-date with latest changes in the Godot ecosystem.
The overview of supported releases has therefore been removed from this page, please consult the stable branch for up-to-date information.
Godot's release policy is in constant evolution. What is described below is intended to give a general idea of what to expect, but what will actually happen depends on the choices of core contributors, and the needs of the community at a given time.
Godot loosely follows Semantic Versioning with a
major.minor.patch versioning system, albeit with an interpretation of each
term adapted to the complexity of a game engine:
majorversion is incremented when major compatibility breakages happen which imply significant porting work to move projects from one major version to another.
For example, porting Godot projects from Godot 2.1 to Godot 3.0 required running the project through a conversion tool, and then performing a number of further adjustments manually for what the tool could not do automatically.
minorversion is incremented for feature releases which do not break compatibility in a major way. Minor compatibility breakage in very specific areas may happen in minor versions, but the vast majority of projects should not be affected or require significant porting work.
The reason for this is that as a game engine, Godot covers many areas such as rendering, physics, scripting, etc., and fixing bugs or implementing new features in a given area may sometimes require changing the behavior of a feature, or modifying the interface of a given class, even if the rest of the engine API remains backwards compatible.
Upgrading to a new minor version is therefore recommended for all users, but some testing is necessary to ensure that your project still behaves as expected in a new minor version.
patchversion is incremented for maintenance releases which focus on fixing bugs and security issues, implementing new requirements for platform support, and backporting safe usability enhancements. Patch releases are backwards compatible.
Patch versions may include minor new features which do not impact the existing API, and thus have no risk of impacting existing projects.
Updating to new patch versions is therefore considered safe and strongly recommended to all users of a given stable branch.
major.minor combinations stable branches. Each stable branch
starts with a
major.minor release (without the
patch) and is
further developed for maintenance releases in a Git branch of the same name
(for example patch updates for the 3.3 stable branch are developed in the
3.3 Git branch).
As mentioned in the introduction, Godot's release policy is evolving, and
earlier Godot releases may not have followed the above rules to the letter.
In particular, the 3.2 stable branch received a number of new features in
3.2.2 which would have warranted a
minor version increment.
Release support timeline¶
Stable branches are supported at minimum 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.