Exclude <4.3 builds, allow more time to startup (macOS)

Author: Bromeon

.github/other/check-example.sh

@@ -12,7 +12,7 @@ set -euo pipefail
 # Opening in editor can take a while (import reosurces, load extensions for the first time, ...).
 # Unlike EXAMPLE_TIMEOUT, this is an upper bound, after which CI job fails, so not the entire time is necessarily spent.
 EXAMPLE_TIMEOUT=5
-EDITOR_TIMEOUT=30 # already encountered 20s on macOS CI.
+EDITOR_TIMEOUT=60 # already encountered 20s on macOS CI.
 
 example="$1"
 if [ -z "$example" ]; then

.github/workflows/ci.yml

@@ -177,23 +177,16 @@ jobs:
             artifact-name: linux-4.3
             godot-binary: godot.linuxbsd.editor.dev.x86_64
 
-          - name: linux-4.2
-            os: ubuntu-22.04
-            artifact-name: linux-4.2
-            godot-binary: godot.linuxbsd.editor.dev.x86_64
-            rust-extra-args: --features godot/api-4.2
-
-          - name: linux-4.1
-            os: ubuntu-22.04
-            artifact-name: linux-4.1
-            godot-binary: godot.linuxbsd.editor.dev.x86_64
-            rust-extra-args: --features godot/api-4.1
-
-          # Do not run memchecks; increases CI complexity too much with the patching and everything.
-          # Such cases need to be tested in the itest suite in the main repo.
-
-          # Also don't test double precision. Makes a lot of code more difficult to write (real conversions etc), missing
-          # the point of examples being approachable. Users who need it are trusted to adjust code based on compile errors.
+          # Deliberately don't include:
+          #
+          # * Memchecks: increases CI complexity too much with the patching and everything.
+          #   Such cases need to be tested in the itest suite in the main repo.
+          #
+          # * Double precision. Makes a lot of code more difficult to write (real conversions etc), missing the point of examples
+          #   being approachable. Users who need it are trusted to adjust code based on compile errors.
+          #
+          # * Godot versions older than latest stable: require "least common denominator" compromises, not being able to showcase new features.
+          #   Also, opening projects in newer editor versions frequently causes warnings.
 
 
     steps:

ReadMe.md

@@ -23,6 +23,16 @@ We currently feature the following example projects:
   Showcases how classes and their state can be hot-reloaded in the Godot editor.
 
 
+## Godot version
+
+Examples are written to work with **latest stable** Godot version. When a new minor/patch version is released, we generally try to update it
+within a few days or weeks.
+
+We additionally run CI with newer in-dev versions, but that support is best-effort. Examples do not provide compatibility with older Godot
+versions, as the projects need migration and this would prevent us from showcasing newer versions. godot-rust itself however offers support
+for older versions, see [Compatibility and Stability][book-compatibility].
+
+
 ## Contributions
 
 If you would like to contribute an example, please open an issue **before** submitting a big pull request.
@@ -38,3 +48,5 @@ Like the library, all contributions are subject to the [Mozilla Public License 2
 [Website]: https://godot-rust.github.io
 [Book]: https://godot-rust.github.io/book
 [mpl]: https://www.mozilla.org/en-US/MPL
+[book-compatibility]: https://godot-rust.github.io/book/toolchain/compatibility.html
+```