Browse Source

Merge pull request #10125 from tetrapod00/release-policy-36

Update Release Policy for release of 3.6
Max Hilbrunner 9 months ago
parent
commit
7729d98280
1 changed files with 5 additions and 5 deletions
  1. 5 5
      about/release_policy.rst

+ 5 - 5
about/release_policy.rst

@@ -218,11 +218,11 @@ Maintenance (patch) releases are released as needed with potentially very
 short development cycles, to provide users of the current stable branch with
 short development cycles, to provide users of the current stable branch with
 the latest bug fixes for their production needs.
 the latest bug fixes for their production needs.
 
 
-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).
+The 3.6 release is out, and may be the last stable branch of Godot 3.x. It is 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). There is a
+development branch for 3.x, which may become 3.7, but it has no ETA.
 
 
 What are the criteria for compatibility across engine versions?
 What are the criteria for compatibility across engine versions?
 ---------------------------------------------------------------
 ---------------------------------------------------------------