yes it would be automatic, and just like now if you have changed code
the svn tool created version change files that have to be resolved if
you have changed core.
Before making such changes it will give you a list of these and ask if
you want to do an automatic upgrade. this is to catch those changes that
were not done in best practices.
Hopefully the best practices has been followed and all the changes are
in the hot-deploy, in which case there is nothing the upgrade will
touch, in hot-deploy.
Also for such conditions it would be best to run the migration against a
copy of the productions.
james_sg sent the following on 8/23/2010 8:47 PM:
=========================
BJ Freeman <http://bjfreeman.elance.com>
Strategic Power Office with Supplier Automation
<http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com <http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Hi BJ,
Are you proposing a function to do automatic version upgrade?
If so, how will it affects those OFBiz instances that are customized?
Regards,
James
BJ Freeman wrote:
ofbiz at this point offers a rudimentary migration doc, thanks to the
mostly Jacques effort.
But let me give you an idea of what I experience with my BBS free
software.
1)the upgrade you download puts the software in a non access mode from
the web.
2)it evaluate what version you are running
3)it then goes to the software site and generate a download of files and
database changes, as a script.
4)after you install the files it rechecks that everything in there and
does a database migration.
5) it runs tests to validate crucial operations.
6) it then tells you to remove the folder with the upgrade which
unblocks the web access.
now for ofbiz I see those steps as
1) add a service that stops web access while upgrade
2) notes and stores the current svn version
3) upgrades from the latest branch that is a release(by version number)
4) checks database against upgrades and reports what has to be done
manually if any. then is the hardest part.
5) keeps rechecking till the database passes configure test.
6) gives a message to restart ofbiz or issues a restart command.
any thoughts
