02-28-2017, 08:35 PM
The answer is yes and no. The thing is that 5.5 brought coreBOS updater:
http://corebos.org/documentation/doku.php?id=en:devel:corebosupdater
and that changed everything. Thanks to this module we all of sudden do not need to migrate ever again, coreBOS has become a continuous development process. Whenever we need to make database changes we add a changeset, when you do a "git pull" and update your code, coreBOS updater will sync all necessary/pending database changes, so migrations do not exist and neither do version numbers. Version numbers have become a mere marketing tool. The real version number is the git commit number you are on and that changes every day, in fact most days it changes various times.
In short, do not look at the version number, sync your code with the github repository and update frequently. I have many clients upgrading monthly, some even more frequently, others when they need it but I really recommend not wating more than a few months....
keep asking if it is not clear.
Once again, all you have to do to migrate to the latest version of coreBOS is:
- copy your database to a new install of the latest code
- execute update_tabdata and create_userfiles
- login, go to coreBOS updater: load and apply all
similar to this but easier
http://corebos.org/documentation/doku.php?id=en:upgradevt2cb
http://corebos.org/documentation/doku.php?id=en:devel:corebosupdater
and that changed everything. Thanks to this module we all of sudden do not need to migrate ever again, coreBOS has become a continuous development process. Whenever we need to make database changes we add a changeset, when you do a "git pull" and update your code, coreBOS updater will sync all necessary/pending database changes, so migrations do not exist and neither do version numbers. Version numbers have become a mere marketing tool. The real version number is the git commit number you are on and that changes every day, in fact most days it changes various times.
In short, do not look at the version number, sync your code with the github repository and update frequently. I have many clients upgrading monthly, some even more frequently, others when they need it but I really recommend not wating more than a few months....
keep asking if it is not clear.
Once again, all you have to do to migrate to the latest version of coreBOS is:
- copy your database to a new install of the latest code
- execute update_tabdata and create_userfiles
- login, go to coreBOS updater: load and apply all
similar to this but easier
http://corebos.org/documentation/doku.php?id=en:upgradevt2cb
Joe
TSolucio
TSolucio