as far as UI yes.
as far as steps no. what was shown was setup but not migration.
coming from a background of doing complete desktop/server roll-outs for
large corporations, I am looking more of doing diffs, compares then
generate the needed changes.
One of those steps is to create new database initialize the tables then
do and db to db migration.
From past experience this could take a day or more for very large
databases.
then a final re-sync for new data and a switch to new code that my
requires changing the Virtual Apache settings.
=========================
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
james_sg sent the following on 8/26/2010 2:57 AM:
seems something like
http://wiki.openbravo.com/wiki/Upgrading_Openbravo_installations#Using_the_upgraders
and http://www.openbravo.com/product/demo-center/erp/
BJ Freeman wrote:
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.
