Main Branch Upgrade & SVN to Git Migration Issues

0
Hi All, I have a Mendix project with the following setup: Main branch: 9.8.0 Other branches: 9.24.16 I want to: Upgrade the main branch from 9.8.0 to 9.24.40 Migrate the project from SVN to Git after the upgrade My concerns: Will the version mismatch between main and other branches cause problems during migration? What is the safest way to clone the main branch for upgrade without affecting the original? Any best practices for aligning all branches after the main branch upgrade before Git migration? Appreciate any guidance or experiences you can share. Thanks!
asked
2 answers
1

Hi Reemali,

Having different Mendix versions between your main branch (9.8.0) and other branches (9.24.16) won’t immediately block the SVN to Git migration, as the migration process primarily depends on the repository structure rather than Mendix version compatibility. However, it’s strongly recommended to align all branches to the same Mendix version before migration to prevent future merge conflicts or model inconsistencies once you’re in Git. The safest way to upgrade your main branch is to first clone it in SVN (for example, create a new branch called “Main_Upgrade_Test”) and perform the upgrade to 9.24.40 on that clone. This approach lets you validate the upgrade, fix any issues, and ensure stability before applying the changes to your original main branch. After confirming that the upgrade works smoothly, you can merge your other branches (currently on 9.24.16) into the upgraded main branch to align all branches on the same version. It’s also a good idea to clean up outdated or unused branches before migration, as well as ensure your MPR file size and number of commits are within Git migration limits. Finally, once all branches are aligned and tested, proceed with the migration to Git. This sequence—test upgrade, align branches, clean repository, then migrate—minimizes risks and ensures a smooth and stable transition from SVN to Git.

 

Hope it helps!

answered
0

Hi Reemali Patil,

 

Try these steps,

 

Clone the Main Branch

  •  Create a separate working copy of the main branch
  •  Perform the upgrade here so production code stays unaffected

 

Complete the Mendix Version Upgrade First

  • Upgrade main to 9.24.x
  •  Run App > Check Widgets, fix deprecations, update Marketplace modules
  • Fully test main branch before merging anything else

 

Align Other Branches

  • After upgrade is stable, merge changes from main into all active long-living branches
  • Resolve version conflicts (common for Atlas/UI modules and marketplace dependencies)

 

Migrate to Git (once everything is aligned)

  • Migrate the entire repository at once
  • Take advantage of Git branching afterwards (better collaboration + faster merges)

 

Why this order?

  •  Reduces risk of breaking in-flight development
  •  Avoids version mismatch conflicts during Git migration
  • Easier rollback because you keep a backup of the original 9.8.x SVN setup
answered