| 1 | = Godot 4 Migration Plan |
| 2 | |
| 3 | == Pre-Planning |
| 4 | 1. Research GDExtension replacing GDNative |
| 5 | 1. Research any breaking changes introduced in GDScript |
| 6 | |
| 7 | == Deployment |
| 8 | 1. Move code onto a 3.x branch |
| 9 | 1. Move Godot studio files onto a 3.x branch |
| 10 | 1. Fork Godot core, move existing into a 3.x folder |
| 11 | 1. Install Godot 4 |
| 12 | 1. Install Zylann for GD4 |
| 13 | 1. Rebuild everything |
| 14 | 1. Profit |
| 15 | |
| 16 | = Migration Rollout |
| 17 | How to upgrade to Godot 4? all at once or partial upgrade in phases? |
| 18 | |
| 19 | Dev snapshot is [https://godotengine.org/article/dev-snapshot-godot-4-0-alpha-4 presently in Alpha 4 release], they state there will be breaking changes between alpha releases due to the fact it is not feature-complete yet. |
| 20 | |
| 21 | == Partial Migration |
| 22 | Kevin works on v3.x, Jon works on v4; Kevin migrates to v4 when it has stabilized. |
| 23 | |
| 24 | ||= Pros =||= Cons =|| |
| 25 | ||Kevin can continue learning||Need to maintain separate code repositories for each version|| |
| 26 | || ||Risk of diverging alignment and vision|| |
| 27 | || ||Kevin will have to throw-away / address even more technical debt when he migrates to v4|| |
| 28 | |
| 29 | == Full Migration |
| 30 | Both Kevin and Jonathan migrate to Godot 4 at the same time, no phased upgrade. |
| 31 | |
| 32 | ||= Pros =||= Cons =|| |
| 33 | ||Kevin and Jonathan can integrate immediately||Breaking changes with new alpha release for Kevin's work|| |
| 34 | || ||Lack of tutorials available for Godot 4 front-end (GDScript)|| |