OpenUpgrade developer module features
Proposed features of the OpenUpgrade developer module (openupgrade_
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Analyse model and field properties more sophisticatedly:
- Report on differences in _table and _sequence properties
- Improve the reporting on renamed modules and fields, as well as models and fields that were moved to another module
- Detect XML IDS that were moved to another module (e.g.
Analyse module properties more sophisticatedly:
- Report on differences in dependencies and use this information to detect delegated or integrated functionality.
Parse data items and report the following information:
- Any attribute that is present in old, but not in new (e.g. the domain on stage types in the CRM module 6.1). This should hint the developer to load a data item that overwrites the attribute with an empty value (if the field is still present).
- Report on permissions that were changed globally per group on the various models
(e.g. "sales user now has write permission on partners")
It is good to have an overview of differences between subsequent versions of OpenERP (when run on non-customized databases) as well as for the user to know what permissions have been changed on his or hers customized database.
Code generation: as the analysis becomes more refined, we can probably start generating some code for the developer to review.
- Create XML definitions that overwrite attributes that were removed
- Generate the defaults/