openupgrade-drivers team mailing list archive

["Stefan Rijnhart \(Therp\)" <question227533@xxxxxxxxxxxxxxxxxxxxx>]

Question #227533 on OpenUpgrade Server changed:
https://answers.launchpad.net/openupgrade-server/+question/227533

    Status: Open => Answered

Stefan Rijnhart (Therp) proposed the following answer:
1. No, OpenERP expands the version with the major version (if it does
not include it). So your module version comes out as 6.1.1.0. The
migration folder 6.1.1.1 is therefore not consulted because 6.1.1.1
signifies a later version than 6.1.1.0. You can work around this by
including the major release version in your module version. Note that
this does not work in earlier versions than 6.0: having '5.0.1.1' as a
module version in OpenERP 5.0 comes out as '5.0.5.0.1.1'.

2. As indicated above, the version number of the module for 6.1 should not be lower than the version of the installed database on 6.0 because in that case the migration scripts do not run. As for conventions, use your own. Version numbers of official addons often do not even change from one release to another. FYI best practices for community modules are proposed here: 
https://lists.launchpad.net/openerp-community/msg02170.html

-- 
You received this question notification because you are a member of
OpenUpgrade Drivers, which is an answer contact for OpenUpgrade Server.