Política de lanzamiento de Godot

La politica de lanzamiento de Godot está en una progresiva evolución. Lo que se describió debajo con el propósito de dar una idea general de las expectativas, pero lo que de hecho sucederá depende de los contribuyentes centrales, y las necesidades de la comunidad en un momento dado.

Versionado de Godot

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:

  • The major version is incremented when major compatibility breakages happen which imply significant porting work to move projects from one major version to another.

    Por ejemplo, los puertos de proyectos de Godot de Godot 2.1 a Godot 3.0 requiere correr el proyecto a través de una herramienta de conversión, y entonces realizando un numero de procedimientos de ajustes manualmente por lo que la herramienta no podria hacerlo de forma automática.

  • The minor version 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.

Truco

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.

  • The patch version 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.

    Las versiones Parche deberán incluir nuevas características menores que no impactaran en la API existente, y por lo tanto no corren riesgo de impactar en los proyectos existentes.

Truco

La actualización a nuevas versiones de parche es por lo tanto considerada segura y fuertemente recomendada a todos los usuarios de una rama estable dada.

We call major.minor combinations stable branches. Each stable branch starts with a major.minor release (without the 0 for 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).

Nota

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.

Línea de tiempo del soporte de liberación

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. This is the case for the 2.1 branch, and will be the case for the latest 3.x stable branch by the time Godot 4.0 is released.

Versión

**Fecha de publicación*

Nivel de soporte

Godot 4.0

~2021 (ver abajo)

"inestable" Enfoque actual del desarrollo (inestable).

Godot 3.4

Q2 or Q3 2021

supported Beta. Receives new features as well as bug fixes while under development.

Godot 3.3

April 2021

supported Receives fixes for bugs, security and platform support issues, as well as backwards-compatible usability enhancements.

Godot 3.2

Enero de 2020

eol No longer supported as fully superseded by the compatible 3.3 release (last update: 3.2.3).

Godot 3.1

Marzo de 2019

|parcial| Sólo arreglos de la plataforma críticos, de seguridad y de soporte (ultima versión: 3.1.2).

Godot 3.0

Enero de 2019

eol Esta versión ya no es sostenida (Ultima actualización: 3.0.6).

Godot 2.1

Julio de 2016

|parcial| Sólo arreglos de la plataforma críticos, de seguridad y de soporte (ultima versión: 2.1.6).

Godot 2.0

Febrero de 2016

eol Esta versión ya no es sostenida (ultima actualización: 2.0.4.1).

Godot 1.1

Mayo de 2015

eol Sin soporte.

Godot 1.0

Diciembre de 2014

eol Sin soporte.

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

Las versiones de Godot anteriores al lanzamiento no están pensadas para ser utilizadas en la producción y se proporcionan solo con el propósito de realizar pruebas.

¿Cuándo sale el próximo lanzamiento?

While Godot contributors aren't working under any deadlines, we have historically had one major or minor release per year, with several maintenance updates between each.

Empezando con Godot 3.3, nosotros apuntamos a acelerar nuestros ciclos de desarrollo para lanzamientos menores, por lo que puedes esperar un lanzamiento menor cada 3 o 6 meses.

Los lanzamientos de mantenimiento (parches) van a ser lanzados cuando sean necesitados por un ciclo de desarrollo potencialmente corto, para proveer a los usuarios de la rama estable actual de las ultimas correcciones de bugs para sus necesidades de producción.

As for the upcoming Godot 4.0, we can only say that we aim for a 2021 release, but any closer estimate is likely to be hard to uphold. Alpha builds will be published as soon as the main features for Godot 4.0 are finalized.