From 6dd3e059d67c0de52d2e6a968d4e1033f318523c Mon Sep 17 00:00:00 2001 From: github-actions <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 9 Nov 2023 21:10:12 +0000 Subject: [PATCH] [UPD] HTML documentation --- docs/020_required_knowledge.html | 36 ++++++++++++++++++++++++++++++-- docs/index.html | 6 +++++- docs/searchindex.js | 2 +- 3 files changed, 40 insertions(+), 4 deletions(-) diff --git a/docs/020_required_knowledge.html b/docs/020_required_knowledge.html index 27a063046a29..f53dc6c2e8a3 100644 --- a/docs/020_required_knowledge.html +++ b/docs/020_required_knowledge.html @@ -47,7 +47,11 @@
TODO : write here prerequisites.
+you should be able to launch an instance of Odoo on your local PC, +or on your server, for each version of your migration.
You should know how to get openupgradelib, obtained from the source repository, installed in your Python environment that is going to run the instance.
You should know how to invoke the odoo executable, injecting arguments for loading server wide modules and migrations path. +For example, if you’re migrating from version 12.0 to 16.0, +you should be able to launch Odoo versions 13.0, 14.0, 15.0 and 16.0.
If you’re migrating to a recent version, +you’ll certainly have to reference numerous open pull requests on OCA/OpenUpgrade, +for the modules installed on your instance. +In this case, using the gitaggregate +tool greatly facilitates the management of these numerous pull requests.
If you want to develop migration scripts for a given module, you need to have +complete functional (and technical) knowledge of this module. +For example, to develop migration scripts for account module from version 12.0 +to 13.0, you need to master how account is working in version 12.0 and how +account is working in version 13.0.
Knowledge of SQL is a must if you need to write fast queries on huge amounts of data.
you need to have a good understanding of the functions provided +by the openupgradelib library.