openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #01906
Re: release schedule for new features in trunk
Hello,
It's true that there is a mechanism that helps updating the schema of
the database inside the OpenERP framework. (it does not do everything
but good part of the schema, not the data). It's usefull when you
develop new modules but not sufficient to migrate from one version to
another.
But to migrate your instance, you will need an OpenERP Enterprise
contract which includes: migration of the database (schema+data) and all
services required for this (testing, support for changes, bugs...).
Migration of OpenERP is quite complex (like any ERP in the world) that's
why it's a service. A part of this service is automated through our
migration plateform (http://migration.openerp.com) but we still need
several days for each migration because every instance is different.
We also have a service to migrate custom or community module. Our goal
is to make community modules sustainable in the long term by having
prices like 80 EUR to migrate an accounting localisation:
- port the code to the new version
- upgrade data+schema
- migration service
More info here:
http://v6.openerp.com/node/1311
Thanks,
On 01/02/2013 02:16 AM, Phillip Frost wrote:
> On Jan 1, 2013, at 6:02 PM, Dale E. Moore wrote:
>
>> Have you looked at the community data migration project here? I have not yet evaluated using it for migrating version 6 DBs to version 7, but; I am hopeful.
>
> I have now, but to clarify, this system is not yet in production, so migration now isn't such a concern. My concern is migrations in the future.
>
> I would say the official documentation [1] is unclear, and even contrary on the fact that migration is a service only available to hosted or enterprise customers. Even an official service provider I dealt with was unable to explain this to me despite being directly asked, and despite consulting with their contacts at OpenERP SA. I would urge OpenERP SA to be more forthcoming in this respect.
>
> [1] http://doc.openerp.com/v6.1/developer/11_upgrade_and_migration.html
> "The creation (or modification in the case of an upgrade) of SQL tables is automated thanks to the description of objects in the server."
> "The upgrade from version to version is automatic and doesn’t need any special scripting on the user’s part."
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help : https://help.launchpad.net/ListHelp
--
Fabien Pinckaers
CEO OpenERP
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
Follow ups
References