Make a 0.9.4 release

[ghost]

While we're working on 0.10 on master, it's not quite ready yet. Meanwhile, Godot 3.3 came out, and we might want to update the 0.9 branch and set the default API version to it (#728). There are also a number of non-breaking PRs that we might want to backport there:

• Add automatically_derived and allow lints in macros #701
• TypedArray: mention use cases and limitations in doc #710
• Add VariantArray duplicate method for deep copy #711
• Vectors: Default, missing Vector2 constants, documentation #718
• Impl NodeExt for TRef #727
• Implemented some additional API functions related to crate::core_type… #729
• InitHandle and NativeClass::new_instance() now refer to a global class registry to check if the class has been added. #737

We can probably create a 0.9 branch and cherry-pick commits there. This does not mean that we're going to support 0.9 indefinitely: only before 0.10 is actually ready.

Unresolved question: how CI works in this case?

[Bromeon]

Do we have a 0.9 branch already? We might need create an alternative timeline in the past, as #713 and possibly others introduced breaking changes, so we can't use master for 0.9.* releases.

[ghost]

We do have a tag. We can branch from there.

[iamwilhelm]

Does godot-rust 0.9.3 support Godot 3.3? I'm wondering if I should wait for godot-rust 0.9.4 before upgrading. The readme says it doesn't support Godot 4, but says nothing about 3.3.

[Demindiro]

Does godot-rust 0.9.3 support Godot 3.3? I'm wondering if I should wait for godot-rust 0.9.4 before upgrading. The readme says it doesn't support Godot 4, but says nothing about 3.3.

As far as I can tell it works with 3.3. I haven't encountered any issues with it.

[jacobsky]

@Bromeon This issue appears to be a smidge on the stale side, are you still interested in working on a 0.9.4 release or do you think we should skip it all together and focus on working towards the 0.10.0 release?

[Bromeon]

Might still be worth making a 0.9.4 release (also to test CI), but we should probably triage which items are backported. I would say we focus on important bugfixes and small QoL additions, but nothing that creates huge merge conflicts (such as features built on top of the new glam vectors).

[drager]

Any news? Now there's even a 3.4: https://github.com/godotengine/godot/releases/tag/3.4.2-stable

[Bromeon]

We already support Godot 3.4 on master branch, besides many other improvements.

We are currently finalizing the 0.10 release, with only very few issues left:
https://github.com/godot-rust/godot-rust/milestones/v0.10.0

As many APIs have improved significantly since 0.9.3 (sometimes in breaking ways), I think it makes most sense to focus our resources on the upcoming 0.10 branch. I will thus close this issue, but feel free to ask further questions 🙂

[drager]

We already support Godot 3.4 on master branch, besides many other improvements.

We are currently finalizing the 0.10 release, with only very few issues left: https://github.com/godot-rust/godot-rust/milestones/v0.10.0

As many APIs have improved significantly since 0.9.3 (sometimes in breaking ways), I think it makes most sense to focus our resources on the upcoming 0.10 branch. I will thus close this issue, but feel free to ask further questions slightly_smiling_face

Great! Just tried against master and it works! Thanks!