You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[IMP] data: match data versions to release versions
This commit fixes two issues at once.
Issue 1
-------
Currently, the migration process will ONLY run if the version of the original
data (in json) is smaller than the last version set in the source code
(`CURRENT_VERSION`). This means that any additional step set outside of the
library is not run without incrementing CURRENT_VERSION in o-spreadsheet.
Example:
- we bump the latest version to 25 in o-spreadsheet;
- we push that value in Odoo
- users start creating spreadsheets in that version so their spreadsheets are
set to version 25
- later on, we need to add a migration step for whatever reason in Odoo, we
assign it to 25.1
=> the migration code will check against the latest version in the source (25)
vs the one in the spreadsheet data (25 as well) and will simply skip the
migration.
So 25.1 will never run...
Issue 2
-------
The current scheme of the incremented integer is impractical when it comes
to figure out which odoo version it matches(*).
Knowing the release version is usefull for bug fixes to know which version of
the code generated the json data.
With this commit, data format version are now aligned with odoo versions
Current master is 18.3. Next, it'll be 18.4, 19.0, 19.1, etc.
(*) o-spreadsheet releases follow the same version numbers as odoo releases.
closes#5973
Task: 4659206
Signed-off-by: Pierre Rousseau (pro) <[email protected]>
0 commit comments