Changes between Initial Version and Version 1 of Platform/Godot4/Migration


Ignore:
Timestamp:
05/16/22 05:56:05 (3 years ago)
Author:
Jonathan Neufeld
Comment:

Introduction of Godot 4 Migration Planning, currently iterating on the pros/cons of partial vs. full migration plan

Legend:

Unmodified
Added
Removed
Modified
  • Platform/Godot4/Migration

    v1 v1  
     1= Godot 4 Migration Plan
     2
     3== Pre-Planning
     41. Research GDExtension replacing GDNative
     51. Research any breaking changes introduced in GDScript
     6
     7== Deployment
     81. Move code onto a 3.x branch
     91. Move Godot studio files onto a 3.x branch
     101. Fork Godot core, move existing into a 3.x folder
     111. Install Godot 4
     121. Install Zylann for GD4
     131. Rebuild everything
     141. Profit
     15
     16= Migration Rollout
     17How to upgrade to Godot 4? all at once or partial upgrade in phases?
     18
     19Dev 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
     22Kevin 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
     30Both 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)||