Porting Odoo Modules

• Common Migration Helpers
  • Creating Pull Requests in batch
  • Switching off unported modules
  • Updating odoo version in files
  • Reviewing odoo updates
  • Reviewing module source
  • Other tools
• 13.0- → 14.0+
  • OCA’s checklist
  • New API
  • Selection
  • Point of Sale
  • DINAR
• 12.0- → 13.0+
  • OCA’s checklist
  • New API
  • web_settings_dashboard
  • nvd3
  • external_dependencies
  • company_ids in res.users
  • console.log(‘ok’)
  • DINAR
• 11.0- → 12.0+
  • OCA’s checklist
  • New API
  • DINAR
• 10.0- → 11.0+, py2 → py3, shared Settings, sudo.get_param()
  • New API
  • New references
  • Python 3
  • DINAR
• 9.0- → 10.0+, __openerp__.py → __manifest__.py
  • New API
  • New references
  • DINAR
• 7.0- → 8.0+, (cr, uid, ids, context) → self.env
  • Automatic replacements
  • Semi-Automatic replacements

Note

Porting Modules is a process of adapting module to new version. E.g. we have module for odoo 10.0 and we want to make module work in odoo 11.0

Word porting is sometimes replaced to migration. So, don’t confuse it with Data Migration.