Contributors mailing list archives


Re: Add module version numbers guideline

Elico Corp, Eric Caudal
- 06/08/2015 10:16:28
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 08/06/2015 03:53 PM, wrote:
<blockquote cite="" type="cite">
I agree with this rationale, as said on the PR.


2015-08-06 9:38 GMT+02:00 Daniel Reis <>:

Hello all,

There is a proposal to add a guideline for module version numbers for OCA contributions.
Is a nutshell, after some discussion the current proposal is to use 5 version numbers, for example: "".
The two first numbers ones for the Odoo target version.: "8.0".
The next three ones for the module 's semantic version "x.y.z" ("breaking.feature.fix").


«It is unfortunate that most modules don't include in the manifest the information of the major Odoo version they target. This is an important information since most of the time modules are incompatible with other Odoo version other than the one they target.
For example: it is frequent to find code in GitHub with an Odoo module in a "master" branch, but can't be sure of what Odoo version it targets by looking at it's manifest file.

This is so because in the past Odoo/Openerp automatically added the major version to module versions. Thus if your module was version "6.1.1", it would be displayed as "".

It is no longer the case: now Odoo does not do that if the major version is already appended to the module version!

Thus the Odoo target version can be included in the module version without being duplicated by the loading functions, and properly document the module's Odoo target version.»

Please join the discussion on the GitHub Pull Request and leave your comments there:

Thank you
Daniel Reis

Post to: