OpenERP 版本发布常见问题

OpenERP 主要有2个系列：Stable 系列（5.0, 6.0, 6.1, …）这个系列适合生产部署，Trunk 系列 这是一个开发中的版本，准备演化到下一个稳定版。 stable 系列是属于维护状态，意味着不再接受新需求改进或新的功能，但仍会继续修正BUG。 相反, trunk 系列可能会有新的功能和改进，因而通常不适合生产部署。

以下是关于版本发布常见问题列表。

  1. 什么时候发布新的 稳定版/主分支？ 还有版本号是如何命名？

The frequency of major stable releases has fluctuated in the past, but the current policy is to release a new stable version every 6 months on average, with one out of three stable versions being a Long Term Support (LTS) version. An LTS version is normal stable version, but one that is supported for an extended time under the OpenERP Publisher’s Warranty (OPW). Stable versions are labelled as a decimal number with 2 components (e.g. 6.1), where the leftmost part indicates the corresponding Long Term Support (LTS) version, and the second digit indicates successive stable releases between two LTS versions.

作为一个展示，这是一些预期发布特征的列表：

  • 09/2011: 6.1

  • 03/2012: 6.2

  • 09/2012: 7.0 LTS

  • 03/2013: 7.1

  1. How long are LTS version actually supported? And what do you mean exactly by ‘supported’?

The OpenERP Publisher’s Warranty contract covers the 3 last LTS version in parallel. This means that when a new LTS version is released, an older version reaches its end-of-life, and is not supported anymore. As an example, 6.0 LTS will be supported along with 7.0 LTS and 8.0 LTS, but will reach end-of-life when 9.0 LTS is released. The OPW contract defines the kind of support you get for each covered version. This usually includes unlimited bug fixes. You can also read in detail our bug correction policy here: http://doc.openerp.com/v6.0/contribute/11_bug_tracker.html#bug-management-policy

  1. LTS版本和其他主要版本的区别是什么？更新流程是否不同？

Apart from the extended support period, a LTS version is just a normal major version. Any major version introduces many new features and improvements, and some changes that may not be fully compatible with previous version. This is true for non-LTS major versions too. For each major version, you can upgrade via OPW’s migration services.

  1. 子版本/补丁版本和主要版本的区别是什么？更新流程是否不同？

Major versions introduce new features and may not be directly compatible with previous stable series. As a result, a complete migration process has to be followed when going from one major version to the next. This is available via the OPW. Minor versions only introduce bug corrections, but no new features, so the upgrade procedure is built-in in OpenERP Server. You simply need to restart the server once with the additional options “-d -u all”.

提示

参见 安装 获取更多关于升级过程的详情。

  1. When are minor/patch versions released? How are they numbered? Where can the release schedule be found?

Minor versions (a.k.a. patch versions) do not follow a fixed schedule, but are instead released as soon as our OPW team considers that important bugs have been corrected, or that a large number of smaller corrections are now available. If very important issues are discovered one after the other, it may be possible for several patch versions to be released quite close to each other. Minor versions are labelled with 3 numbers (e.g. 6.1.2) where the 2 leftmost numbers correspond to the major release, and the last number indicates successive minor releases between two LTS versions. The most recent minor version (the one with the highest 3rd number) is the recommended one for all production environments. As there is no fixed release schedule, it is not possible to publish it beforehand. The series of milestones on Launchpad are just prospective dates, and may change without notice.

  1. 我非常需要一个稳定bug修复，但是在子版本中没有任何一个有包含这样的修复，我该怎么办？

If the bug has already been corrected in the corresponding stable series, it means that you can already download it from the source repository on Launchpad, and apply it to your installation. If you prefer to have a full installation package, you can contact the OPW team via your usual OPW channel and explain why this bug requires a faster release. We also plan to provide very soon a nightly build system so that the latest code for each series can always be downloaded as a full installer, without waiting for a formally tagged release.