Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: Add module version numbers guideline
by
Andrei Levin
Inside our company we use another semantic meaning for last three numbers, so "x.y.z" is model.code.xml for us. This way we know if application should be reloaded (like in case of model change) and module updated, just reloaded (in case of code change), just updated (in case of xml change). It is very for a production environment where not always you can tear down the application any time you want. Cheers Andrei 2015-08-06 11:08 GMT+02:00 Daniel Reis <dgreis@sapo.pt>: >> One question, I understand the need for the major version number, but >> regarding the semantic version number is there any benefit to add such >> complexity if there is no easy way to download a module in a specific >> version (git tags, x.y.z.tar.gz) for the user? > Answered here: > https://github.com/OCA/maintainer-tools/pull/100#issuecomment-128298061 > > --DR > > _______________________________________________ > Mailing-List: http://odoo-community.org/groups/oca-contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: http://odoo-community.org/groups?unsubscribe -- Didotech Srl Via T.Aspetti, 248 35133 Padova (PD) Tel 049 8592286 Cell.: 347-2426694 www.didotech.com
Reference
-
Add module version numbers guideline
byClosingAp Open Source Integrators Europe, LDA, Daniel Reis-
Re: Add module version numbers guideline
byClosingAp Open Source Integrators Europe, LDA, Daniel Reis -
Re: Add module version numbers guideline
byTecnativa. S. L., Pedro M. Baeza