如何将OpenERP 5.0升级到6.0 [英] How to upgrade OpenERP 5.0 to 6.0

问题描述

我安装了带有一些自定义模块的OpenERP 5.0，希望将其升级到OpenERP 6.0.

I have an OpenERP 5.0 installation with a few custom modules, that I wish to upgrade to OpenERP 6.0.

我对这种软件有一定的经验，并且已经检查过OpenERP.不幸的是，我没有OpenERP的实际经验，我想寻求一些帮助以避免错误.在研究此问题时，我发现有几种策略(ETL流程，数据升级模块)...我想我需要检查所有自定义模块.

I have some experience with this kind of sofware and I have inspected OpenERP. Sadly, I don't have actual experience with OpenERP, and I like to ask for some help in order to avoid mistakes. When researching this, I found there are several strategies (ETL processes, data-upgrade modules)... I assume I'll need to review all custom modules.

将OpenERP 5.0安装升级到6.0的准则或最佳做法是什么?

What are the guidelines or best practice in order to upgrade an OpenERP 5.0 installation to 6.0?

推荐答案

我们仍在计划从5.0到6.0的迁移，因此我对此过程没有任何个人经验.我们计划自己解决问题，但是我们已经进行了很多定制开发，因此我们对OpenERP代码非常满意.如果我听起来像是从别人那里继承了系统，那么支持合同会给我很大的诱惑，该合同包括为您进行迁移.

We're still planning our migration from 5.0 to 6.0, so I don't have any personal experience with the process. We are planning to tackle the work ourselves, but we've done a lot of custom development, so we're pretty comfortable with the OpenERP code. If I were inheriting the system from someone else as it sounds like you are, I would be very tempted by the support contract that includes doing migrations for you.

除了付费服务外，似乎还有一个开源工具可用于运行数据迁移. 几个 那里 是 a

In addition to the paid service, there also appears to be an open-source tool available for running data migrations. It is also discussed in several forum posts. (There really are a lot.)

我们的暂定计划是:

1. 尝试将演示数据库的迁移工具从纯5.0迁移到纯6.1.
2. 按照 Pragtech准则.
3. 扩展迁移工具的配置，以涵盖我们的自定义模块以及该工具未包含的其他模块.
4. 在整个数据库上将迁移运行到沙箱中，并进行测试.
5. 启动并庆祝！

1. Try out the migration tool for a demo database from plain 5.0 to plain 6.1.
2. Migrate the code for our custom modules to 6.1, following the Pragtech guidelines.
3. Extend the migration tool's configuration to cover our custom modules and any others that weren't included with the tool.
4. Run the migration on our full database into a sandbox and test the heck out of it.
5. Launch and celebrate!

更新:

我们已经开始了迁移过程，并且使用的是 OpenUpgrade 而不是Domsense工具.我们从来没有真正看过Domsense工具，所以我不能说哪个更好.到目前为止，我对OpenUpgrade非常满意.

We've started our migration process, and we're using OpenUpgrade instead of the Domsense tool. We never really looked at the Domsense tool, so I can't say which is better. I'm very happy with OpenUpgrade so far.

通常，我发现6.1版比5.0版更容易自定义.到目前为止，我还没有更改任何核心模块.例如，在核心模块插入记录的大多数地方，它会调用助手方法来准备数据.如果添加要填充的新列，则可以覆盖该帮助程序方法.例如，我们在几个表中添加了一个分组字段，然后将其从销售订单行复制到库存移动.我们覆盖了 sale模块的sale_order._prepare_order_line_move()的版本，其中

In general, I've found version 6.1 much easier to customize than 5.0 was. So far, I haven't had to change any core modules. For example, most places where a core module inserts a record, it calls a helper method to prepare the data. If you add a new column that you want to be populated, you can just override that helper method. For example, we added a grouping field to several tables and then wanted to copy it from sales order line to stock move. We overrode the sale module's version of sale_order._prepare_order_line_move() with our own version.

我发布了一个有关自定义报告的单独问题.

不利的一面是，我们尝试迁移的每个自定义功能都需要进行一些更改.到目前为止，核心模块一直存在变化，以某种方式破坏了我们的自定义.更改了字段名称，或者更改了屏幕布局，或者更改了整个模型名称.通常，您可以弄清楚如何修复它，但是一切都需要时间.

The down side is that every customized feature we try to migrate requires some change. So far there has always been a change in the core module that somehow breaks our customization. Either a field name changed, or the screen layout changed, or the whole model name changed. You can usually figure out how to fix it, but everything takes time.

这篇关于如何将OpenERP 5.0升级到6.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！