Translations by Victor Yu
Victor Yu has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 517. |
Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.
|
|
| 2014-02-25 |
由于所有的模块都依赖于 *base* ，因此他们也都会被更新。然而，此项操作需要每个数据库的 *Administrator(管理员)* 密码，所以有时候会不能完成更新，特别是当更新会阻止登陆到系统的时候。
|
|
| 2014-02-25 |
由于所有的模块都依赖于 *base* ，因此他们也都会被更新。然而，此项操作需要每个数据库的 *Administrator(管理员)* 密码，所有有时候会不能完成更新，特别是当更新会阻止登陆到系统的时候。
|
|
| 518. |
OpenERP's release policy states that one or two major releases are published from the development version every year. Transitioning to the next major release implies a lot more changes than jumping to another minor release. As the underlying OpenERP data structures usually evolve quite a bit from one major release to the next, a full migration of the existing data is needed. Each major release will be published with specific recommendations and procedures for upgrading an existing OpenERP system to the next major version.
|
|
| 2014-02-25 |
OpenERP的发行策略表明，每年都会有一到两个主要版本从开发阶段到发行阶段。迁移到下个主要版本意味着比使用其他小的版本更新拥有更多的变化。由于底层的OpenERP数据结构从一个主要版本到下一个主要版本变更都比较多，有必要做全面的数据迁移。每个主要发行版本将会将会制定推荐的从现有OpenERP系统升级到下一主要版本的流程。
|
|
| 519. |
Major Release
|
|
| 2014-02-24 |
主发行版本
|
|
| 520. |
For major releases, it is usually not possible to skip one release, for example upgrading directly from OpenERP 4.2 to OpenERP 6.0. If you need to do such an upgrade, you will simply have to do each intermediary upgrade one after the other.
|
|
| 2014-02-24 |
对于主发行版本，通常是没有办法跳过某个版本的，比如直接从OpenERP4.2升级到OpenERP 6.0。 如果需要的话，你需要做这样的升级的话，最简单的办法应当是作为中介，完成每一个版本的升级，从而到达你想要的版本。
|
|
| 521. |
Upgrade; OpenERP (Windows)
|
|
| 2014-02-10 |
升级; OpenERP (Windows)
|
|
| 522. |
OpenERP Web (Windows)
|
|
| 2014-02-10 |
OpenERP Web (Windows)
|
|
