#291 version number upgrade 1.9.* to 1.11


Issues with version numbers when upgrading 1.9 to 1.11 :
- Upgrade tool records 1.10 as new version number for courses (table cl_cours) instead of 1.11 and thus upgrade_conf restarts at the end of the process
- Upgrade tool checks dbversion 1.10 against new platform version 1.11 and thus "Upgrade done" is never accessed
- "upgrade done message" says new version is 1.10
Suggestion: maybe it would be better to add a specific upgrade procedure for 1.9 to 1.11 instead of mixing 1.10 and 1.11. Even if db version are the same for 1.10 and 1.11, it would be less confusing for platform administrators


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks