[6.1] Major release is always prepended to module version number

[Stefan Rijnhart (Opener)]

Whereas the major release in openerp/modules/migration.py is not taken into account if a module version starts with it (when calculating which versions should be migrated), the major release is always prepended when storing a module version number in the database.

Consider the following:

Major release: 6.1
Installed module version number: 6.1.1.0
Installed module version number in the database: 6.1.6.1.1.0
New module version number: 6.1.1.1

In the migration manager's version number breakdown, 6.1.6.1.1.0 is larger than 6.1.1. As a result, migration scripts of minor module version updates do not run.

Affecting OpenERP 6.1. Fixed in OpenERP 7.0, revision 4718.

I am linking this bug to OpenUpgrade-server 6.1 as well as it should replace "^6.1.6.1." with "6.1." in existing module versions in the database.