From 4b9932748f50ef49cc07bae5bc521e03f3f91f4f Mon Sep 17 00:00:00 2001 From: Tom Date: Tue, 1 Oct 2024 15:25:17 +0200 Subject: [PATCH] Updated Studio Pro version number --- .../developerportal/general/team-server/migrate-to-git.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/developerportal/general/team-server/migrate-to-git.md b/content/en/docs/developerportal/general/team-server/migrate-to-git.md index ed9e9350012..8bbe4fd0646 100644 --- a/content/en/docs/developerportal/general/team-server/migrate-to-git.md +++ b/content/en/docs/developerportal/general/team-server/migrate-to-git.md @@ -18,7 +18,7 @@ Git is a more modern version control system that has several advantages over SVN To be able to migrate your app to Git, your app needs to meet the following criteria: -* The main line ('main') branch in the app is Mendix version 9.24.11 or above +* The main line ('main') branch in the app is Mendix version 9.24.28 or above * All branches in the app are Mendix version 9.12 or above * Current version control is in Team Server SVN * The size of the `.mpr` file for the latest revision of your app and the total number of commits in your version control history fall in one of these two categories: @@ -34,7 +34,7 @@ Only a user with the Scrum Master role can migrate an app. For more information, ## How Migration Works -If your main line is Mendix version 9.24.11 or above, and your team role is Scrum Master, you see a notification on a possible migration at the top of the **Team Server** page for your app. Click **Migrate to Git** to check for migration eligibility and to start the migration. +If your main line is Mendix version 9.24.28 or above, and your team role is Scrum Master, you see a notification on a possible migration at the top of the **Team Server** page for your app. Click **Migrate to Git** to check for migration eligibility and to start the migration. During migration all app history, including revisions for all branches, is copied from SVN to Git.