godotengine/godot-docs-l10n
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs-l10n.git synced 2026-01-05 14:10:19 +03:00
Code Issues Packages Projects Releases Wiki Activity
Files
36b62d0d10ca25bd911d650da42a938cd61f3c28
godot-docs-l10n/sphinx/templates/about/release_policy.pot
Rémi Verschelde 36b62d0d10 Sync Sphinx and Weblate templates with current docs
2023-11-21 12:56:52 +01:00

447 lines
19 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2014-present Juan Linietsky, Ariel Manzur and the Godot community (CC BY 3.0)
# This file is distributed under the same license as the Godot Engine package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Godot Engine latest\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-21 12:44+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../docs/about/release_policy.rst:4
msgid "Godot release policy"
msgstr ""
#: ../../docs/about/release_policy.rst:6
msgid "Godot's release policy is in constant evolution. The description below provides 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."
msgstr ""
#: ../../docs/about/release_policy.rst:12
msgid "Godot versioning"
msgstr ""
#: ../../docs/about/release_policy.rst:14
msgid "Godot loosely follows `Semantic Versioning <https://semver.org/>`__ with a ``major.minor.patch`` versioning system, albeit with an interpretation of each term adapted to the complexity of a game engine:"
msgstr ""
#: ../../docs/about/release_policy.rst:18
msgid "The ``major`` version is incremented when major compatibility breakages happen which imply significant porting work to move projects from one major version to another."
msgstr ""
#: ../../docs/about/release_policy.rst:22
msgid "For example, porting Godot projects from Godot 3.x to Godot 4.x requires running the project through a conversion tool, and then performing a number of further adjustments manually for what the tool could not do automatically."
msgstr ""
#: ../../docs/about/release_policy.rst:26
msgid "The ``minor`` version is incremented for feature releases that 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."
msgstr ""
#: ../../docs/about/release_policy.rst:31
msgid "This is because Godot, as a game engine, covers many areas like rendering, physics, and scripting. Fixing bugs or implementing new features in one area might sometimes require changing a feature's behavior or modifying a class's interface, even if the rest of the engine API remains backwards compatible."
msgstr ""
#: ../../docs/about/release_policy.rst:38
msgid "Upgrading to a new minor version is recommended for all users, but some testing is necessary to ensure that your project still behaves as expected."
msgstr ""
#: ../../docs/about/release_policy.rst:42
msgid "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."
msgstr ""
#: ../../docs/about/release_policy.rst:47
msgid "Patch versions may include minor new features which do not impact the existing API, and thus have no risk of impacting existing projects."
msgstr ""
#: ../../docs/about/release_policy.rst:52
msgid "Updating to new patch versions is therefore considered safe and strongly recommended to all users of a given stable branch."
msgstr ""
#: ../../docs/about/release_policy.rst:55
msgid "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 4.0 stable branch are developed in the ``4.0`` Git branch)."
msgstr ""
#: ../../docs/about/release_policy.rst:62
msgid "Release support timeline"
msgstr ""
#: ../../docs/about/release_policy.rst:64
msgid "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."
msgstr ""
#: ../../docs/about/release_policy.rst:69
msgid "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."
msgstr ""
#: ../../docs/about/release_policy.rst:75
msgid "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."
msgstr ""
#: ../../docs/about/release_policy.rst:81
msgid "**Version**"
msgstr ""
#: ../../docs/about/release_policy.rst:81
msgid "**Release date**"
msgstr ""
#: ../../docs/about/release_policy.rst:81
msgid "**Support level**"
msgstr ""
#: ../../docs/about/release_policy.rst:83
msgid "Godot 4.2 (`master`)"
msgstr ""
#: ../../docs/about/release_policy.rst:83
msgid "November 2023 (estimate)"
msgstr ""
#: ../../docs/about/release_policy.rst:83
msgid "|unstable| *Development.* Receives new features, usability and performance improvements, as well as bug fixes, while under development."
msgstr ""
#: ../../docs/about/release_policy.rst:122
#: ../../docs/about/release_policy.rst:122
#: ../../docs/about/release_policy.rst:122
msgid "unstable"
msgstr ""
#: ../../docs/about/release_policy.rst:86
msgid "Godot 4.1"
msgstr ""
#: ../../docs/about/release_policy.rst:86
msgid "July 2023"
msgstr ""
#: ../../docs/about/release_policy.rst:86
#: ../../docs/about/release_policy.rst:89
#: ../../docs/about/release_policy.rst:95
msgid "|supported| Receives fixes for bugs and security issues, as well as patches that enable platform support."
msgstr ""
#: ../../docs/about/release_policy.rst:119
#: ../../docs/about/release_policy.rst:119
#: ../../docs/about/release_policy.rst:119
#: ../../docs/about/release_policy.rst:119
#: ../../docs/about/release_policy.rst:119
#: ../../docs/about/release_policy.rst:119
msgid "supported"
msgstr ""
#: ../../docs/about/release_policy.rst:89
msgid "Godot 4.0"
msgstr ""
#: ../../docs/about/release_policy.rst:89
msgid "March 2023"
msgstr ""
#: ../../docs/about/release_policy.rst:92
msgid "Godot 3.6 (`3.x`, LTS)"
msgstr ""
#: ../../docs/about/release_policy.rst:92
msgid "Q3 2023 (estimate)"
msgstr ""
#: ../../docs/about/release_policy.rst:92
msgid "|supported| *Beta.* Receives new features, usability and performance improvements, as well as bug fixes, while under development."
msgstr ""
#: ../../docs/about/release_policy.rst:95
msgid "Godot 3.5"
msgstr ""
#: ../../docs/about/release_policy.rst:95
msgid "August 2022"
msgstr ""
#: ../../docs/about/release_policy.rst:98
msgid "Godot 3.4"
msgstr ""
#: ../../docs/about/release_policy.rst:98
msgid "November 2021"
msgstr ""
#: ../../docs/about/release_policy.rst:98
msgid "|eol| No longer supported, as fully superseded by the compatible 3.5 release (last update: 3.4.5)."
msgstr ""
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
#: ../../docs/about/release_policy.rst:121
msgid "eol"
msgstr ""
#: ../../docs/about/release_policy.rst:101
msgid "Godot 3.3"
msgstr ""
#: ../../docs/about/release_policy.rst:101
msgid "April 2021"
msgstr ""
#: ../../docs/about/release_policy.rst:101
msgid "|eol| No longer supported, as fully superseded by the compatible 3.4 release (last update: 3.3.4)."
msgstr ""
#: ../../docs/about/release_policy.rst:104
msgid "Godot 3.2"
msgstr ""
#: ../../docs/about/release_policy.rst:104
msgid "January 2020"
msgstr ""
#: ../../docs/about/release_policy.rst:104
msgid "|eol| No longer supported (last update: 3.2.3)."
msgstr ""
#: ../../docs/about/release_policy.rst:106
msgid "Godot 3.1"
msgstr ""
#: ../../docs/about/release_policy.rst:106
msgid "March 2019"
msgstr ""
#: ../../docs/about/release_policy.rst:106
msgid "|eol| No longer supported (last update: 3.1.2)."
msgstr ""
#: ../../docs/about/release_policy.rst:108
msgid "Godot 3.0"
msgstr ""
#: ../../docs/about/release_policy.rst:108
msgid "January 2018"
msgstr ""
#: ../../docs/about/release_policy.rst:108
msgid "|eol| No longer supported (last update: 3.0.6)."
msgstr ""
#: ../../docs/about/release_policy.rst:110
msgid "Godot 2.1"
msgstr ""
#: ../../docs/about/release_policy.rst:110
msgid "July 2016"
msgstr ""
#: ../../docs/about/release_policy.rst:110
msgid "|eol| No longer supported (last update: 2.1.6)."
msgstr ""
#: ../../docs/about/release_policy.rst:112
msgid "Godot 2.0"
msgstr ""
#: ../../docs/about/release_policy.rst:112
msgid "February 2016"
msgstr ""
#: ../../docs/about/release_policy.rst:112
msgid "|eol| No longer supported (last update: 2.0.4.1)."
msgstr ""
#: ../../docs/about/release_policy.rst:114
msgid "Godot 1.1"
msgstr ""
#: ../../docs/about/release_policy.rst:114
msgid "May 2015"
msgstr ""
#: ../../docs/about/release_policy.rst:114
#: ../../docs/about/release_policy.rst:116
msgid "|eol| No longer supported."
msgstr ""
#: ../../docs/about/release_policy.rst:116
msgid "Godot 1.0"
msgstr ""
#: ../../docs/about/release_policy.rst:116
msgid "December 2014"
msgstr ""
#: ../../docs/about/release_policy.rst:120
#: ../../docs/about/release_policy.rst:120
msgid "partial"
msgstr ""
#: ../../docs/about/release_policy.rst:124
msgid "**Legend:** |supported| Full support – |partial| Partial support – |eol| No support (end of life) – |unstable| Development version"
msgstr ""
#: ../../docs/about/release_policy.rst:130
msgid "Pre-release Godot versions aren't intended to be used in production and are provided for testing purposes only."
msgstr ""
#: ../../docs/about/release_policy.rst:135
msgid "See :ref:`doc_upgrading_to_godot_4` for instructions on migrating a project from Godot 3.x to 4.x."
msgstr ""
#: ../../docs/about/release_policy.rst:141
msgid "Which version should I use for a new project?"
msgstr ""
#: ../../docs/about/release_policy.rst:143
msgid "We recommend using Godot 4.x for new projects, as the Godot 4.x series will be supported long after 3.x stops receiving updates in the future. One caveat is that a lot of third-party documentation hasn't been updated for Godot 4.x yet. If you have to follow a tutorial designed for Godot 3.x, we recommend keeping :ref:`doc_upgrading_to_godot_4` open in a separate tab to check which methods have been renamed (if you get a script error while trying to use a specific node or method that was renamed in Godot 4.x)."
msgstr ""
#: ../../docs/about/release_policy.rst:151
msgid "If your project requires a feature that is missing in 4.x (such as GLES2/WebGL 1.0), you should use Godot 3.x for a new project instead."
msgstr ""
#: ../../docs/about/release_policy.rst:157
msgid "Should I upgrade my project to use new engine versions?"
msgstr ""
#: ../../docs/about/release_policy.rst:161
msgid "Upgrading software while working on a project is inherently risky, so consider whether it's a good idea for your project before attempting an upgrade. Also, make backups of your project or use version control to prevent losing data in case the upgrade goes wrong."
msgstr ""
#: ../../docs/about/release_policy.rst:166
msgid "That said, we do our best to keep minor and especially patch releases compatible with existing projects."
msgstr ""
#: ../../docs/about/release_policy.rst:169
msgid "The general recommendation is to upgrade your project to follow new *patch* releases, such as upgrading from 4.0.2 to 4.0.3. This ensures you get bug fixes, security updates and platform support updates (which is especially important for mobile platforms). You also get continued support, as only the last patch release receives support on official community platforms."
msgstr ""
#: ../../docs/about/release_policy.rst:175
msgid "For *minor* releases, you should determine whether it's a good idea to upgrade on a case-by-case basis. We've made a lot of effort in making the upgrade process as seamless as possible, but some breaking changes may be present in minor releases, along with a greater risk of regressions. Some fixes included in minor releases may also change a class' expected behavior as required to fix some bugs. This is especially the case in classes marked as *experimental* in the documentation."
msgstr ""
#: ../../docs/about/release_policy.rst:183
msgid "*Major* releases bring a lot of new functionality, but they also remove previously existing functionality and may raise hardware requirements. They also require much more work to upgrade to compared to minor releases. As a result, we recommend sticking with the major release you've started your project with if you are happy with how your project currently works. For example, if your project was started with 3.5, we recommend upgrading to 3.5.2 and possibly 3.6 in the future, but not to 4.0+, unless your project really needs the new features that come with 4.0+."
msgstr ""
#: ../../docs/about/release_policy.rst:195
msgid "When is the next release out?"
msgstr ""
#: ../../docs/about/release_policy.rst:197
msgid "While Godot contributors aren't working under any deadlines, we strive to publish minor releases relatively frequently."
msgstr ""
#: ../../docs/about/release_policy.rst:200
msgid "In particular, after the very length release cycle for 4.0, we are pivoting to a faster paced development workflow, with the 4.1 release expected within late Q2 / early Q3 2023."
msgstr ""
#: ../../docs/about/release_policy.rst:204
msgid "Frequent minor releases will enable us to ship new features faster (possibly as experimental), get user feedback quickly, and iterate to improve those features and their usability. Likewise, the general user experience will be improved more steadily with a faster path to the end users."
msgstr ""
#: ../../docs/about/release_policy.rst:209
msgid "Maintenance (patch) releases are released as needed with potentially very short development cycles, to provide users of the current stable branch with the latest bug fixes for their production needs."
msgstr ""
#: ../../docs/about/release_policy.rst:213
msgid "The 3.6 release is still planned and should be the last stable branch of Godot 3.x. It will be a Long-Term Support (LTS) release, which we plan to support for as long as users still need it (due to missing features in Godot 4.x, or having published games which they need to keep updating for platform requirements)."
msgstr ""
#: ../../docs/about/release_policy.rst:220
msgid "What are the criteria for compatibility across engine versions?"
msgstr ""
#: ../../docs/about/release_policy.rst:224
msgid "This section is intended to be used by contributors to determine which changes are safe for a given release. The list is not exhaustive; it only outlines the most common situations encountered during Godot's development."
msgstr ""
#: ../../docs/about/release_policy.rst:228
msgid "The following changes are acceptable in patch releases:"
msgstr ""
#: ../../docs/about/release_policy.rst:230
msgid "Fixing a bug in a way that has no major negative impact on most projects, such as a visual or physics bug. Godot's physics engine is not deterministic, so physics bug fixes are not considered to break compatibility. If fixing a bug has a negative impact that could impact a lot of projects, it should be made optional (e.g. using a project setting or separate method)."
msgstr ""
#: ../../docs/about/release_policy.rst:235
msgid "Adding a new optional parameter to a method."
msgstr ""
#: ../../docs/about/release_policy.rst:236
msgid "Small-scale editor usability tweaks."
msgstr ""
#: ../../docs/about/release_policy.rst:238
msgid "Note that we tend to be more conservative with the fixes we allow in each subsequent patch release. For instance, 4.0.1 may receive more impactful fixes than 4.0.4 would."
msgstr ""
#: ../../docs/about/release_policy.rst:242
msgid "The following changes are acceptable in minor releases, but not patch releases:"
msgstr ""
#: ../../docs/about/release_policy.rst:244
msgid "Significant new features."
msgstr ""
#: ../../docs/about/release_policy.rst:245
msgid "Renaming a method parameter. In C#, method parameters can be passed by name (but not in GDScript). As a result, this can break some projects that use C#."
msgstr ""
#: ../../docs/about/release_policy.rst:247
msgid "Deprecating a method, member variable, or class. This is done by adding a deprecated flag to its class reference, which will show up in the editor. When a method is marked as deprecated, it's slated to be removed in the next *major* release."
msgstr ""
#: ../../docs/about/release_policy.rst:251
msgid "Changes that affect the default project theme's visuals."
msgstr ""
#: ../../docs/about/release_policy.rst:252
msgid "Bug fixes which significantly change the behavior or the output, with the aim to meet user expectations better. In comparison, in patch releases, we may favor keeping a buggy behavior so we don't break existing projects which likely already rely on the bug or use a workaround."
msgstr ""
#: ../../docs/about/release_policy.rst:256
msgid "Performance optimizations that result in visual changes."
msgstr ""
#: ../../docs/about/release_policy.rst:258
msgid "The following changes are considered **compatibility-breaking** and can only be performed in a new major release:"
msgstr ""
#: ../../docs/about/release_policy.rst:261
msgid "Renaming or removing a method, member variable, or class."
msgstr ""
#: ../../docs/about/release_policy.rst:262
msgid "Modifying a node's inheritance tree by making it inherit from a different class."
msgstr ""
#: ../../docs/about/release_policy.rst:263
msgid "Changing the default value of a project setting value in a way that affects existing projects. To only affect new projects, the project manager should write a modified ``project.godot`` instead."
msgstr ""
#: ../../docs/about/release_policy.rst:267
msgid "Since Godot 5.0 hasn't been branched off yet, we currently discourage making compatibility-breaking changes of this kind."
msgstr ""
#: ../../docs/about/release_policy.rst:272
msgid "When modifying a method's signature in any fashion (including adding an optional parameter), a GDExtension compatibility method must be created. This ensures that existing GDExtensions continue to work across patch and minor releases, so that users don't have to recompile them. See `pull request #76446 <https://github.com/godotengine/godot/pull/76446>`_ for more information."
msgstr ""
#: ../../docs/<rst_epilog>:0
msgid "Translation status"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink