03:15 - Generate a Ready to Deploy Odoo Add-on Directly from UML Diagram
Akhmad Daniel SembiringDone
12:00 - Asynchronous e-commerce cart with offline mode
09:30 - Beyond Odoo Development Essentials
10:00 - How To Contribute Code to the OCA - Technical
10:30 - Odoo and the NewRetail Revolution: Navigating the Future with SmartPOS, Kiosks, KDS and much more
Luis F MiléoDone
11:30 - Server Management: Harnessing the Power of Remote Server Control
David Jimenez GomarizDone
11:00 - How to organize an Odoo project as a regular Python app
04:00 - On the potential of Large Language Models for the Odoo ecosystem and beyond
Frederik Kramer and Ruben OrtlamDone
10:00 - Odoo incoming mailing configuration and testing
11:00 - Defining the proper reconciliation of payment providers.
hugues de keyzer is a software developer with more than 20 years of experience. passionate about free software, he joined coop it easy in 2021, where his work includes module development, code porting, infrastructure management, automation and database migration. he has migrated several client databases across multiple versions, and he is eager to share with you the trauma that this has caused him.
ok, we’ve all heard about openupgrade. it’s great. but concretely, how are we supposed to use it? how can it be used to migrate a database across multiple versions?
this talk will first give the big picture of how this all works, then dive into the nitty-gritty details so that you can do it too without tearing your hair out.
EXTRA COMMENTS FOLLOWING THE TALKS:* the 20 years of experience of hugues de keyzer is not in free software development, just software development in general. * openupgrade is not a reverse engineering of odoo’s upgrade. the migration scripts are deduced from a static datamodel change analysis and functional observations. * about noupdate data: not all of it is overwritten, only the data that has actually changed in odoo between versions. * website pages are converted as much as possible, but some incompatible ones should be removed. * make sure to keep a backup of the database as it was before the migration. this will be useful if, at a later time, you need to recover data that was lost during the migration.