[ADD] odoo_sh: Mention Python dependency behavior in FAQ

Odoo.sh doesn't use the requirements.txt included in Odoo but Python
packages available in the Linux distribution instead. This is
non-obvious and can be confusing to users, especially in the cases where
the version available in the distribution and requirements.txt are
different.

Adding this section is intended to clarify that, and to provide a
reference for developers of custom modules on what to expect.

opw-2688205

.gitignore

@@ -4,7 +4,6 @@
 
 # Sphinx build files
 _build/
-extensions/odoo_theme/static/style.css
 
 # Dependencies
 odoo

Makefile

@@ -9,6 +9,10 @@ ifndef BUILD_DIR
   BUILD_DIR    = _build
 endif
 
+ifndef CURRENT_LANG
+  CURRENT_LANG = en
+endif
+
 SPHINX_BUILD   = sphinx-build
 CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
@@ -18,7 +22,6 @@ SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSIO
 				 -j $(WORKERS)
 SOURCE_DIR     = content
 
-
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/13.0
@@ -43,7 +46,7 @@ clean:
 	rm -rf $(BUILD_DIR)/*
 	@echo "Cleaning finished."
 
-html: $(BUILD_DIR)/html/_static/style.css
+html: $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
 	@echo "Build finished."
@@ -63,10 +66,10 @@ gettext:
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
 	@echo "Generation finished."
 
-$(BUILD_DIR)/html/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
+$(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
 	@echo "Compiling stylesheets..."
-	mkdir -p $(BUILD_DIR)/html/_static
-	pysassc extensions/odoo_theme/static/style.scss $(BUILD_DIR)/html/_static/style.css
+	mkdir -p $(HTML_BUILD_DIR)/_static
+	pysassc extensions/odoo_theme/static/style.scss $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Compilation finished."
 
 #=== Development and debugging rules ===#
@@ -74,6 +77,6 @@ $(BUILD_DIR)/html/_static/style.css: extensions/odoo_theme/static/style.scss ext
 fast: SPHINXOPTS += -A collapse_menu=True
 fast: html
 
-static: $(BUILD_DIR)/static/style.css
-	cp -r extensions/odoo_theme/static/* $(BUILD_DIR)/html/_static/
-	cp -r static/* $(BUILD_DIR)/html/_static/
+static: $(HTML_BUILD_DIR)/static/style.css
+	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
+	cp -r static/* $(HTML_BUILD_DIR)/_static/

conf.py

@@ -290,7 +290,7 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
             for _alternate_version in sorted(_alternate_versions, reverse=True)
             if _alternate_version != version and (
                 _alternate_version != 'master' or pagename.startswith('developer')
-            )
+            ) and not _alternate_version.startswith('saas')
         ]
 
     def _localize():

content/administration.rst

@@ -18,4 +18,5 @@ These guides provide instructions on how to install, maintain and upgrade Odoo d
 
     administration/install
     administration/maintain
+    administration/upgrade
     administration/odoo_sh

content/administration/maintain.rst

@@ -7,8 +7,8 @@ Maintain
 .. toctree::
 
     maintain/update
-    maintain/db_upgrade
     maintain/enterprise
     maintain/hosting_changes
-    maintain/db_premise
+    maintain/online
+    maintain/on_premise
     maintain/supported_versions

content/administration/maintain/db_upgrade.rst

@@ -1,413 +0,0 @@
-
-.. |assistance-contact| replace::
-   If you need Odoo assistance on this matter, please contact your Odoo Account Manager or contact
-   our `Sales department`_.
-.. _Sales department: mailto:sales@odoo.com
-
-.. _db-upgrade:
-
-================
-Versions upgrade
-================
-
-.. _db-upgrade/overview:
-
-Overview
-========
-
-.. _db-upgrade/process:
-
-The upgrade process
--------------------
-
-This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers.
-
-.. _db-upgrade/definition:
-
-Definition
-~~~~~~~~~~
-
-An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)
-
-An upgrade does not cover:
-
-* changing :ref:`Editions <db-upgrade/faq/editions-change>` (i.e., Community to Enterprise edition)
-* switching :ref:`hosting type <db-upgrade/faq/hosting-types-switch>` (i.e., On-Premise to Online or
-  Odoo.sh)
-* migration from another ERP to Odoo
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/process-workflow:
-
-Process workflow
-~~~~~~~~~~~~~~~~
-
-The upgrade process in a nutshell:
-
-#. You create a test upgrade request.
-#. | The request is processed by Odoo:
-   | This happens via an automated process that runs the database through an upgrade script and
-     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
-     manually and adjust the script specifically to your database until the upgrade succeeds.
-#. Odoo delivers a test database.
-#. You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)
-#. If there are any discrepancies, you report them to the Upgrade support team via the
-   :ref:`Help portal <db-upgrade/test-assistance>`.
-#. We will fix the issues and send you a new test database.
-#. Once you completed the testing and are happy with the result, you decide on a date and time when
-   you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the
-   production upgrade.
-#. Odoo delivers the production database through the automated process.
-#. You restore it in your Production environment a few short hours later and continue working on the
-   newly upgraded database.
-
-.. _db-upgrade/service-level:
-
-Service Level Agreement
------------------------
-
-What is covered by the Enterprise Licence?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
-following service at all times.
-
-The upgrade of:
-
-* standard applications
-* Studio customization (as long as the Studio app is still active)
-* customizations done by our consulting and developer services *if* they are covered by a
-  ‘Maintenance of Customisations’ subscription
-
-The Upgrade Service is limited to the technical conversion and adaptation of your database (standard
-modules and data) to make it compatible with the targeted version.
-
-What upgrading does NOT cover
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* The cleaning of pre-existing data & configuration while upgrading
-* Any new developments and/or upgrade of your own :ref:`custom modules
-  <db-upgrade/faq/custom-modules>`
-* `Training <https://www.odoo.com/learn>`_ on the new version
-
-You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
-Agreement <upgrade>` page.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/get-started:
-
-Get started
-===========
-
-The upgrade process varies depending on where your database is hosted.
-
-.. _db-upgrade/online:
-
-Online (SaaS)
--------------
-
-If you are hosted Online, please check your `database manager <https://www.odoo.com/my/databases>`_.
-
-.. _db-upgrade/odoo-sh:
-
-Odoo.sh
--------
-
-If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade
-<../odoo_sh/advanced/upgrade_your_database>`.
-
-.. _db-upgrade/on-premise:
-
-On-Premise
-----------
-
-There are two possibilities:
-
-#. Via the interface of our `website form <https://upgrade.odoo.com>`_
-#. | For technically-advanced users and partners, via the following command line (to be used on the
-     machine where your database is hosted):
-   | ``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d <your db name> -t 14.0``
-
-What does it do?
-~~~~~~~~~~~~~~~~
-
-The above command will dump your database to a file, then send it to the upgrade platform for
-upgrade, displaying you the live logs, then restore the upgraded database back on your server as a
-duplicate test database.
-
-.. _db-upgrade/steps:
-
-Steps
-=====
-
-.. _db-upgrade/steps-test:
-
-The testing phase
------------------
-
-.. _db-upgrade/test-process:
-
-Test process
-~~~~~~~~~~~~
-
-Also referred to as the pre-production phase, the test phase allows you to review an upgraded
-version of your database without affecting your production database in any way.
-
-We suggest that you run the test upgrade process at least once, but you can do it as often as you
-want (one at a time).
-
-Once you receive your upgraded test database, you should check that all data, processes and
-functionality are still correct and working as expected.
-
-If you do find discrepancies, you'll be able to:
-
-* | :ref:`Report your issues <db-upgrade/test-assistance>`
-  | and/or
-* Ask for a new :ref:`test request <db-upgrade/test-db-request>` after the reported issues have
-  been fixed in the upgrade script.
-
-When you do not find any discrepancies, you'll be able to:
-
-* Move on to the upgrade of your :ref:`production database <db-upgrade/production-live>`.
-
-.. _db-upgrade/test-db-request:
-
-Request a test database
-~~~~~~~~~~~~~~~~~~~~~~~
-
-When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
-
-.. image:: media/db-upgrade-test-purpose.png
-   :align: center
-   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
-
-.. _db-upgrade/test-guidance:
-
-Test guidance
-~~~~~~~~~~~~~
-
-Every business and organization has its own operational needs and will have to test its specific
-Odoo instance respectively. However, we recommend you look at `the test scenario
-<https://drive.google.com/open?id=1Lm4JqbsHBirB1wMi14UChoz_YHLjx5ec>`_ we created, a high-level idea
-of what you should test and look out for.
-
-.. todo:: change link "test scenario" once the related doc is published
-
-.. _db-upgrade/test-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade
-Support:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
-
-   .. image:: media/db-upgrade-test-assistance.png
-      :align: center
-      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
-
-   .. warning::
-      If you choose another *Ticket Description* type, the request will be redirected to another
-      team than the upgrade one and will slow down the processing and response time.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-test-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-.. note::
-   * The purpose of the test phase is not to correct existing data or configurations in your
-     database.
-   * |assistance-contact|
-
-.. _db-upgrade/steps-production:
-
-The production launch
----------------------
-
-.. _db-upgrade/production-live:
-
-Production goes live
-~~~~~~~~~~~~~~~~~~~~
-
-The production upgrade request is when you decide to upgrade your current database with all your
-production data (invoices, VAT returns, inventories, current orders) to a new version of your choice.
-
-After your :ref:`tests <db-upgrade/steps-test>` are completed to your satisfaction, submit the
-request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
-Select *Production* purpose.
-
-.. image:: media/db-upgrade-production-purpose.png
-   :align: center
-   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
-
-.. danger::
-   Going into production without first testing may lead to:
-
-   - business interruptions (e.g. no longer having the possibility to validate an action)
-   - poor customer experiences (e.g. an eCommerce website that does not work correctly)
-
-.. _db-upgrade/production-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **production database**, please contact the **Odoo
-Support**:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select the appropriate type related to your issue but
-   **do not select** the option *An issue related to my upgrade*.
-
-   .. note::
-      After upgrading to production, the support will be provided by the Support team instead of the
-      Upgrade team.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-production-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-   .. warning::
-      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
-      to another team than the support one and will slow down the processing and response time.
-
-.. _db-upgrade/faq:
-
-FAQ
-===
-
-.. _db-upgrade/faq/why:
-
-Why upgrade?
-------------
-
-* You benefit from the latest features of the :ref:`new major version
-  <db-upgrade/faq/release-notes>` released by Odoo.
-* If you are in an :ref:`unsupported version <db-upgrade/supported-versions>`, you get a new version
-  with support.
-
-.. _db-upgrade/faq/when:
-
-When to upgrade?
-----------------
-
-Whenever you want. You can make your upgrade request as soon as a new version is released on our
-`website form <https://upgrade.odoo.com>`_.
-
-.. _db-upgrade/faq/availability:
-
-Availability of the new version
--------------------------------
-
-Please kindly note that as soon as we announce the release of a new major version (usually at the
-end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the
-new version is not immediately available for existing databases.
-
-.. _db-upgrade/faq/finalization:
-
-Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)
----------------------------------------------------------------------
-
-Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so
-many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade,
-and translate to the new structure. If you use multiple apps managing sensitive data (e.g.,
-Accounting, Inventory, etc.), some cases may still require a human intervention, making the process
-slower.
-
-This is especially true during the first months following the release of a new major version, which
-can significantly lengthen the upgrade delay.
-
-In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses
-only CRM will be processed faster than a multi-company, multi-user database that uses Accounting,
-Sales, Purchase, and Manufacturing.
-
-So, in a nutshell, what can impact your upgrade lead time?
-
-* Source & targeted versions
-* Installed apps
-* Volume of data
-* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
-* Installation of new apps or configuration changes after the start of the test phase
-
-Usually, the delays experienced during the first request (waiting time between the time you
-submitted your first request for a test upgrade) can generally give you an idea of the time to wait
-for the production request.
-
-.. _db-upgrade/faq/custom-modules:
-
-Upgrade of the custom modules
------------------------------
-
-As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
-service is subject to additional fees.
-
-If you have a custom code, you can choose to have it upgraded by our services, by one of our
-`partners <https://www.odoo.com/partners>`_ or you can do it yourself.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/editions-change:
-
-Editions change (from Community to Enterprise)
-----------------------------------------------
-
-An upgrade does not cover a change of `Editions <https://www.odoo.com/page/editions>`_
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/hosting-types-switch:
-
-Switching the hosting types (Self-hosted vs Online vs Odoo.sh)
---------------------------------------------------------------
-
-An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
-
-Open the following link to get :doc:`more information about how to change your hosting type
-<hosting_changes>`.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/release-notes:
-
-Release Notes by version
-------------------------
-
-Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
-features and improvements made in each version.
-
-.. _db-upgrade/assistance:
-
-Assistance
-==========
-
-.. _db-upgrade/contact:
-
-Contact our Upgrade service support
------------------------------------
-
-Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
-Upgrade Team <mailto:upgrade@odoo.com>`_. We will be very pleased to answer it as soon as possible.
-
-.. _db-upgrade/supported-versions:
-
-Supported versions
-------------------
-
-Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo.
-
-This is a factor to take into consideration before upgrading. If you are on an older version, we
-suggest you to prefer the most recent version to benefit from a longer support (before having to
-upgrade again).
-
-You can get more information about our :doc:`supported versions <supported_versions>`.

content/administration/maintain/on_premise.rst

@@ -1,9 +1,6 @@
-
-.. _db_premise:
-
-===============================
-On-premises Database management
-===============================
+==============================
+On-premise database management
+==============================
 
 Register a database
 ===================
@@ -21,7 +18,7 @@ Registration Error Message
 If you are unable to register your database, you will likely encounter this
 message:
 
-.. image:: media/error_message_sub_code.png
+.. image:: on_premise/error_message_sub_code.png
     :align: center
     :alt: Something went wrong while registering your database,
           you can try again or contact Odoo Help
@@ -44,14 +41,14 @@ Solutions
   * You can unlink the old database yourself on your `Odoo Contract
     <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
 
-    .. image:: media/unlink_single_db.png
+    .. image:: on_premise/unlink_single_db.png
         :align: center
 
 
     A confirmation message will appear; make sure this is the correct database as
     it will be deactivated shortly:
 
-    .. image:: media/unlink_confirm_enterprise_edition.png
+    .. image:: on_premise/unlink_confirm_enterprise_edition.png
         :align: center
 
 
@@ -65,7 +62,7 @@ Solutions
     <https://accounts.odoo.com/my/subscription>`__, a short message will appear
     specifying which database is problematic:
 
-    .. image:: media/unlink_db_name_collision.png
+    .. image:: on_premise/unlink_db_name_collision.png
         :align: center
 
 
@@ -96,7 +93,7 @@ Error message due to too many users
 If you have more users in your local database than provisionned in your
 Odoo Enterprise subscription, you may encounter this message:
 
-.. image:: media/add_more_users.png
+.. image:: on_premise/add_more_users.png
     :align: center
     :alt: This database will expire in X days, you
           have more users than your subscription allows
@@ -125,7 +122,7 @@ Database expired error message
 If your database reaches its expiration date before your renew your subscription,
 you will encounter this message:
 
-.. image:: media/database_expired.png
+.. image:: on_premise/database_expired.png
     :align: center
     :alt: This database has expired.
 
@@ -157,7 +154,7 @@ You can duplicate your database by accessing the database manager on your
 server (<odoo-server>/web/database/manager). In this page, you can easily
 duplicate your database (among other things).
 
-.. image:: media/db_manager.gif
+.. image:: on_premise/db_manager.gif
     :align: center
 
 
@@ -175,5 +172,5 @@ System Parameters`, we advise you to use a `uuid generator <https://www.uuidtool
 use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any
 other record by clicking on it and using the edit button.
 
-.. image:: media/db_uuid.png
+.. image:: on_premise/db_uuid.png
     :align: center

content/administration/maintain/online.rst

@@ -0,0 +1,143 @@
+=================================
+Online (SaaS) database management
+=================================
+
+To manage a database, sign in to https://www.odoo.com and access the `database management page
+<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
+
+.. image:: online/my-databases.png
+   :align: center
+   :alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
+
+.. note::
+   Make sure you are connected as the administrator of the database you want to manage.
+
+.. image:: online/dropdown-menu.png
+   :align: right
+   :alt: Clicking on the gear icon opens the drop-down menu.
+
+Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
+
+Several actions are available:
+
+- :ref:`online/upgrade`
+- :ref:`online/duplicate`
+- :ref:`online/rename`
+- :ref:`online/download`
+- :ref:`online/domains`
+- :ref:`online/tags`
+- :ref:`online/delete`
+- :ref:`online/contact-support`
+- :ref:`online/users`
+
+.. _online/upgrade:
+
+Upgrade
+=======
+
+Upgrade the database to the latest Odoo version.
+
+.. warning::
+   Upgrading a database to a newer version of Odoo is a complex operation that requires time and
+   caution. It is essential to test the upgrade before upgrading the production database.
+
+.. seealso::
+   - :doc:`../upgrade/process`
+
+.. _online/duplicate:
+
+Duplicate
+=========
+
+Make an exact copy of the database to be able to perform testing without compromising the daily
+operations.
+
+.. important::
+   - By checking *For testing purposes*, all external communication (emails, payments, delivery
+     orders, etc.) are disabled by default on the duplicated database.
+   - Duplicate databases expire automatically after 15 days.
+
+.. _online/rename:
+
+Rename
+======
+
+Rename the database and its URL.
+
+.. _online/download:
+
+Download
+========
+
+Download instantly a ZIP file with a backup of the database.
+
+.. note::
+   Databases are backed up daily according to the `Odoo Cloud SLA
+   <https://www.odoo.com/cloud-sla>`_.
+
+.. _online/domains:
+
+Domains
+=======
+
+Configure custom domains to access the database via another URL.
+
+.. seealso::
+   - :doc:`/applications/websites/website/publish/domain_name`
+
+.. _online/tags:
+
+Tags
+====
+
+Add tags to sort your databases out. You can search the tags in the search bar.
+
+.. _online/delete:
+
+Delete
+======
+
+Delete a database instantly.
+
+.. danger::
+   Deleting a database means that all data is permanently lost. The deletion is instant and for all
+   users. It is recommended to create a backup of the database before deleting it.
+
+Read carefully the warning message that pops up and proceed only if you fully understand the
+implications of deleting a database:
+
+.. image:: online/delete.png
+   :align: center
+   :alt: A warning message is prompted before deleting a database.
+
+.. note::
+   - Only an administrator can delete a database.
+   - The database name is immediately available for a new database.
+   - It is not possible to delete a database if it is expired or linked to a subscription. If
+     needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+   - To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+
+.. _online/contact-support:
+
+Contact Support
+===============
+
+Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
+pre-filled.
+
+.. _online/users:
+
+Invite / Remove Users
+=====================
+
+To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
+users, click on *Add more users*.
+
+.. image:: online/invite-users.png
+   :align: center
+   :alt: Clicking on "Add more users" adds additional email fields.
+
+To remove users, select the users to remove and click on *Remove*.
+
+.. seealso::
+   - :doc:`/applications/general/users/manage_users`

content/administration/maintain/supported_versions.rst

@@ -20,35 +20,37 @@ This matrix shows the support status of every version.
 
 **Major releases are in bold type.**
 
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-|                    | Odoo Online | Odoo.sh  | On-Premise   |   Release date |                                              |
-+====================+=============+==========+==============+================+==============================================+
-| **Odoo 14.0**      |    |green|  | |green|  |   |green|    | October 2020   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 13.0**      |    |green|  | |green|  |   |green|    | October 2019   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 12.saas~3     |    |green|  | N/A      | N/A          | August 2019    |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 12.0**      |    |green|  | |green|  |   |green|    | October 2018   | *End-of-support is planned for October 2021* |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 11.saas~3     |   |orange|  | N/A      | N/A          | April 2018     |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 11.0**      |   |orange|  | |orange| |    |red|     | October 2017   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 10.saas~15    |   |orange|  | N/A      | N/A          | March 2017     |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 10.saas~14    |   |orange|  | N/A      | N/A          | January 2017   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 10.0**      |   |orange|  | |orange| |    |red|     | October 2016   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 9.saas~11     |   |orange|  | N/A      | N/A          | May 2016       |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 9.0**       |   |orange|  | N/A      |    |red|     | October 2015   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 8.saas~6      |   |orange|  | N/A      | N/A          | February 2015  |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 8.0**       |   |orange|  | N/A      |    |red|     | September 2014 |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
++-----------------+-------------+----------+-------------+----------------+------------------------+
+|                 | Odoo Online | Odoo.sh  | On-Premise  | Release date   | End of support         |
++=================+=============+==========+=============+================+========================+
+| **Odoo 15.0**   | |green|     | |green|  | |green|     | October 2021   | October 2024 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 14.0**   | |green|     | |green|  | |green|     | October 2020   | October 2023 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 13.0**   | |green|     | |green|  | |green|     | October 2019   | October 2022 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 12.saas~3  | |orange|    | N/A      | N/A         | August 2019    |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 12.0**   | |orange|    | |orange| | |red|       | October 2018   | October 2021           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 11.saas~3  | |orange|    | N/A      | N/A         | April 2018     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 11.0**   | |orange|    | |orange| | |red|       | October 2017   | October 2020           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~15 | |orange|    | N/A      | N/A         | March 2017     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~14 | |orange|    | N/A      | N/A         | January 2017   |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 10.0**   | |orange|    | |orange| | |red|       | October 2016   | October 2019           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 9.saas~11  | |orange|    | N/A      | N/A         | May 2016       |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 9.0**    | |orange|    | N/A      | |red|       | October 2015   | October 2018           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 8.saas~6   | |orange|    | N/A      | N/A         | February 2015  |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 8.0**    | |orange|    | N/A      | |red|       | September 2014 | October 2017           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
 
 
 .. note::
@@ -64,6 +66,9 @@ This matrix shows the support status of every version.
     🏁 Future version, not released yet
 
 
+.. This is an awful way to display colored circles but "Large Green Circle Emoji" was only released
+   in 2019 (see https://unicode-table.com/en/1F7E2/). Let's wait a few more years...
+
 .. |green| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6IzAwYTcwMCIvPjwvc3ZnPg==
    :width: 15
 

content/administration/odoo_sh/advanced.rst

@@ -9,5 +9,4 @@ Advanced
 
    advanced/containers
    advanced/submodules
-   advanced/upgrade_your_database
    advanced/frequent_technical_questions

content/administration/odoo_sh/advanced/frequent_technical_questions.rst

@@ -30,3 +30,26 @@ We advise that:
   `idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
   cause side-effects if they are started more often than expected.
 
+Why are the installed Python libraries different from Odoo's own requirements.txt?
+----------------------------------------------------------------------------------
+
+On Odoo.sh, Odoo uses the Python libraries available in the Linux distribution
+to fulfill its dependencies. Odoo is compatible with the packages in Debian
+stable and Ubuntu LTS releases. The `requirements.txt <https://github.com/odoo/odoo/blob/master/requirements.txt>`_
+included with Odoo is intended for use on different distributions where the
+same library versions might not be available. As a result, Odoo.sh does not use
+Odoo's own requirements.txt file and there might be occasional differences
+between them.
+
+For example, reportlab 3.5.34 is the version available on Ubuntu 20.04 as a
+distribution package. That distribution uses Python 3.8, in which case
+requirements.txt in `Odoo 14.0 <https://github.com/odoo/odoo/blob/2097c75dc38b310c4d9ddecd79e2218448a51a4c/requirements.txt#L46>`_
+specifies reportlab 3.5.55. Normally speaking the pin in requirements.txt
+should reflect that and be 3.5.34, but it turns out that this version only
+works if Ubuntu's patches are applied to it. Ubuntu LTS releases have
+backporting of bug fixes, which means that the behavior of a Python package in
+the distribution might not be the same as that same version when installed with
+pip. This is the case with reportlab, which is why the pin is different.
+
+If a custom module requires a more recent version of a package than is
+installed on Odoo.sh, you can specify it in your own requirements.txt file.

content/administration/odoo_sh/getting_started/create.rst

@@ -184,4 +184,4 @@ as you can only have one database linked per subscription.
 
 If you plan to make it your production,
 unlink your former database from the subscription, and register the newly imported database.
-Read the :ref:`database registration documentation <db_premise>` for instructions.
+Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions.

content/administration/upgrade.rst

@@ -0,0 +1,12 @@
+:nosearch:
+
+=======
+Upgrade
+=======
+
+.. toctree::
+
+    upgrade/process
+    upgrade/odoo_sh
+    upgrade/service_level
+    upgrade/faq

content/administration/upgrade/faq.rst

@@ -0,0 +1,171 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===
+FAQ
+===
+
+.. _upgrade-faq/why:
+
+Why upgrade
+===========
+
+* You benefit from the latest features of the :ref:`new major version
+  <upgrade-faq/release-notes>` released by Odoo.
+* If you are in an :ref:`unsupported version <upgrade/supported-versions>`, you get a new version
+  with support.
+
+.. _upgrade-faq/when:
+
+When to upgrade
+===============
+
+Whenever you want. You can make your upgrade request as soon as a new version is released or when
+your version turns unsupported, and you still wish to enjoy support.
+
+.. _upgrade-faq/availability:
+
+Availability of the new version
+===============================
+
+As soon as Odoo announces the release of a new major version, you can create a test upgrade request
+to try the latest version. Please note that at this point, the upgrade scripts will only have been
+tested with demo data. Please report any issue you might encounter while testing via the `Odoo
+Support page <https://www.odoo.com/help>`_ and make sure to be happy with your test version before
+requesting the upgrade of your database in production.
+
+.. _upgrade-faq/duration:
+
+Duration of the upgrade
+=======================
+
+It is impossible to give time estimates for every upgrade request.
+
+In general, the "smaller" the database, the quickest the upgrade request is completed. A single-user
+database that uses only CRM will be processed faster than a multi-company, multi-user database that
+uses Accounting, Sales, Purchase, and Manufacturing.
+
+You can expect the time it takes for the platform to upgrade the test database will be similar to
+the production upgrade.
+
+.. _upgrade-faq/project:
+
+The upgrade project
+===================
+
+It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the
+issues encountered that might need to be addressed by our technical team.
+
+So, in a nutshell, what can impact your upgrade lead time?
+
+* Source & targeted versions
+* Installed apps
+* Volume of data
+* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
+* Installation of new apps or configuration changes after the start of the test phase
+* User commitment
+
+.. _upgrade-faq/custom-modules:
+
+Upgrade of the custom modules
+=============================
+
+As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
+service is subject to additional fees.
+
+Depending on your situation, the custom code could be upgraded by our services, by one of our
+partners, or you can do it yourself.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/editions-change:
+
+Editions change (from Community to Enterprise)
+==============================================
+
+The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a
+community or enterprise edition. It is required to have an enterprise subscription to upgrade.
+
+.. note:: |assistance-contact|
+
+.. seealso::
+   - `Editions <https://www.odoo.com/page/editions>`_
+
+.. _upgrade-faq/hosting-types-switch:
+
+Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)
+=================================================================================================
+
+An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
+
+Open the following link to get :doc:`more information about how to change your hosting type
+<../maintain/hosting_changes>`.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/release-notes:
+
+Release Notes by version
+========================
+
+Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
+features and improvements made in each version.
+
+How long is my test available for
+---------------------------------
+
+An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial
+period upon request. For Odoo.sh or on-premise, there is no restriction.
+
+How many tests to perform before upgrading to production?
+---------------------------------------------------------
+
+As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours
+before requesting your production upgrade and test your workflows one last time.
+
+How to/Where to report upgrade issues?
+--------------------------------------
+
+If you encounter issues during the upgrade process, please contact the Odoo Support through the
+`Odoo Support page <https://www.odoo.com/help>`_
+
+- To report an issue discovered during the testing phase, please select **An issue related to my
+  upgrade (test phase)**.
+- To report an issue discovered post-upgrade, please select **An issue related to my upgrade
+  (production)**
+
+Upgrading to production
+-----------------------
+
+Once you have completed testing and are happy with the result, you decide on a date and time when
+you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the
+production upgrade.
+
+
+How is my data handled in the Upgrade Platform?
+-----------------------------------------------
+
+The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services.
+
+Your data is hosted on servers that follow our security guidelines, namely:
+
+- SSL - All web connections to client instances are protected with 256-bit SSL encryption
+  (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our
+  certificate chains are using SHA-2 already.
+- Safe System - Our servers are running recent Linux distribution with up-to-date security patches,
+  with firewall and intrusion countermeasures (not disclosed for obvious reasons).
+
+Servers are located at the same locations as our Cloud providers with the following services:
+
+- Restricted perimeter, physically accessed by authorized data center employees only
+- Physical access control with security badges or biometrical security
+- Security cameras monitoring the data center locations 24/7
+- Security personnel on-site 24/7
+
+The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and
+are permanently deleted following that period.
+
+You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection
+Regulation page <https://www.odoo.com/gdpr>`_.

content/administration/upgrade/odoo_sh.rst

@@ -1,9 +1,7 @@
 
-=====================
-Upgrade your database
-=====================
-
-.. _odoosh-advanced-upgrade_your_database:
+=======================
+Odoo.sh version upgrade
+=======================
 
 Download and Upload your database
 =================================

content/administration/upgrade/process.rst

@@ -0,0 +1,256 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===============
+Upgrade process
+===============
+
+.. _upgrade/overview:
+
+Overview
+========
+
+An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0).
+
+An upgrade does not cover:
+
+* Changing :ref:`editions <upgrade-faq/editions-change>` (i.e., Community to Enterprise edition)
+* Switching :ref:`hosting type <upgrade-faq/hosting-types-switch>` (i.e., On-Premise to Online or
+  Odoo.sh)
+* Migration from another ERP to Odoo
+
+.. note:: |assistance-contact|
+
+.. _upgrade/process-workflow:
+
+Process workflow
+----------------
+
+The upgrade process in a nutshell:
+
+#. You create a test upgrade request.
+#. | Odoo processes the request:
+   | This happens via an automated process that runs the database through an upgrade script and
+     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
+     manually and adjust the script specifically to your database until the upgrade succeeds.
+#. Odoo delivers a test database.
+#. You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)
+#. If there are any discrepancies, you report them to the Upgrade support team via the help portal
+   (see :ref:`upgrade/test-assistance`).
+#. We will fix the issues and send you a new test database.
+#. Once you have completed the testing and are happy with the result, you decide on a date and time
+   when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request
+   for the production upgrade.
+#. Odoo delivers the production database through the automated process.
+#. You restore it in your Production environment a few short hours later and continue working on the
+   newly upgraded database (this is done automatically on SaaS).
+
+.. _upgrade/get-started:
+
+Get started
+===========
+
+The upgrade process varies depending on where your database is hosted.
+
+.. _upgrade/online:
+
+Online Hosting (SaaS)
+---------------------
+
+The upgrade request is made via your `database manager <https://www.odoo.com/my/databases>`_.
+
+.. image:: process/online-access-databases.png
+   :align: center
+   :alt: Click on the profile button then on "My Databases"
+
+.. image:: process/online-upgrade-button.png
+   :align: center
+   :alt: Click on the settings button next to your database, then on "Upgrade"
+
+.. _upgrade/odoo-sh:
+
+Cloud Platform (Odoo.sh)
+------------------------
+
+:doc:`odoo_sh`
+
+.. _upgrade/on-premise:
+
+Self-Hosting (On-Premise)
+-------------------------
+
+There are two possibilities:
+
+#. Via `Odoo Upgrade service <https://upgrade.odoo.com>`_
+#. | For technically advanced users and partners, via the following command line on the machine
+     where your database is hosted:
+   | ``python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target
+     version>``
+
+The above command will dump your database to a file, send it to the upgrade platform for an upgrade,
+display you the live logs, and restore the upgraded database back on your server as a duplicate test
+database.
+
+.. _upgrade/testing-phase:
+
+Testing Phase (pre-production phase)
+====================================
+
+This phase allows you to review an upgraded version of your database without affecting your
+production database in any way.
+
+We suggest that you run the test upgrade process at least once, but you can do it as many times as
+you need (one at a time).
+
+Once you receive your upgraded test database, check that all data, processes, and functionality are
+still correct and working as expected.
+
+If you do find discrepancies, report your issues (see :ref:`upgrade/test-assistance`) and request
+a new test database (see :ref:`upgrade/test-db-request`) when the reported issues are fixed in
+the upgrade script.
+
+If you do not find any discrepancies, you'll be able to move on to the upgrade of your
+:ref:`production database <upgrade/production-live>`.
+
+.. _upgrade/test-db-request:
+
+Request a test database
+-----------------------
+
+When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
+
+.. image:: process/test-purpose.png
+   :align: center
+   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
+
+.. _upgrade/test-guidance:
+
+Test guidance
+-------------
+
+Every business and organization has its own operational needs and has to test its specific Odoo
+instance respectively. We recommend you look at `the test scenario
+<https://docs.google.com/document/d/1ypNs7JKPOsjNbKpdiKFH7Al6g6whZ9jr7f7duAQ5E1w/>` for further
+information.
+
+.. todo:: change link "test scenario" once the related doc is published
+
+.. _upgrade/test-assistance:
+
+Assistance
+----------
+
+If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support
+via the `Odoo Support page <https://www.odoo.com/help>`_.
+
+Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
+
+   .. image:: process/test-assistance.png
+      :align: center
+      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
+
+   .. warning::
+      If you choose another *Ticket Description* type, the request will be redirected to another
+      team. This will slow down the processing and response time.
+
+Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/test-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+.. note::
+   * The purpose of the test phase is not to correct existing data or configurations in your
+     database.
+   * |assistance-contact|
+
+.. _upgrade/steps-production:
+
+The production launch
+---------------------
+
+.. _upgrade/production-live:
+
+Production goes live
+~~~~~~~~~~~~~~~~~~~~
+
+The production upgrade request is when you decide to upgrade your current database with all your
+production data (invoices, VAT returns, inventories, current orders) to a new version of your
+choice.
+
+After your :ref:`tests <upgrade/testing-phase>` are completed to your satisfaction, submit the
+request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
+Select *Production* purpose.
+
+.. image:: process/production-purpose.png
+   :align: center
+   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
+
+.. danger::
+   Going into production without first testing may lead to:
+
+   - business interruptions (e.g., no longer having the possibility to validate an action)
+   - poor customer experiences (e.g., an eCommerce website that does not work correctly)
+
+.. _upgrade/production-assistance:
+
+Assistance
+~~~~~~~~~~
+
+If you encounter issues or problems in the **production database**, please get in touch with **Odoo
+Support**:
+
+#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
+#. Under the *Ticket Description* section, select the appropriate type related to your issue but
+   **do not select** the option *An issue related to my upgrade*.
+
+   .. note::
+      After upgrading to production, the support will be provided by the Support team instead of the
+      Upgrade team.
+
+#. Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+   This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/production-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+   .. warning::
+      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
+      to another team than the support one and will slow down the processing and response time.
+
+.. _upgrade/assistance:
+
+Assistance
+==========
+
+.. _upgrade/contact:
+
+Contact our Upgrade service support
+-----------------------------------
+
+Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
+Upgrade Team <mailto:upgrade@odoo.com>`_. We will be happy to answer it as soon as possible.
+
+.. _upgrade/supported-versions:
+
+Supported versions
+------------------
+
+Please note that Odoo provides support and bug fixing only for the three last major versions of
+Odoo.
+
+This is a factor to take into consideration before upgrading. If you are on an older version, we
+suggest you to prefer the most recent version to benefit from longer support (before having to
+upgrade again).
+
+You can get more information about our :doc:`supported versions <../maintain/supported_versions>`.
+
+.. seealso::
+   - :doc:`faq`
+   - :doc:`odoo_sh`
+   - :doc:`service_level`
+   - :doc:`../maintain/supported_versions`

content/administration/upgrade/service_level.rst

@@ -0,0 +1,37 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+=======================
+Service Level Agreement
+=======================
+
+What is covered by the Enterprise Licence?
+==========================================
+
+Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
+following service at all times.
+
+The upgrade of:
+
+* standard applications
+* Studio customization (as long as the Studio app is still active)
+* customizations done by our consulting and developer services *if* they are covered by a
+  ‘Maintenance of Customisations’ subscription
+
+The Upgrade Service is limited to your database's technical conversion and adaptation (standard
+modules and data) to make it compatible with the targeted version.
+
+What upgrading does NOT cover
+=============================
+
+* The cleaning of pre-existing data & configuration while upgrading
+* Any new developments and/or upgrades of your own :ref:`custom modules
+  <upgrade-faq/custom-modules>`
+* `Training <https://www.odoo.com/learn>`_ on the latest version
+
+You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
+Agreement <upgrade>` page.
+
+.. note:: |assistance-contact|

content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst

@@ -59,7 +59,7 @@ look for the *Colombian Electronic Invoice* section.
 Using the Testing mode it is possible to connect with a Carvajal T&S
 testing environment. This allows users to test the complete workflow
 and integration with the CEN Financiero portal, which is accessible
-here: https://cenfinancierolab.cen.biz
+here: https://cenflab.cen.biz/site/
 
 Once that Odoo and Carvajal T&S is fully configured and ready for
 production the testing environment can be disabled.

content/applications/finance/accounting/fiscal_localizations/localizations/colombia_ES.rst

@@ -57,12 +57,11 @@ Configuración de las credenciales del Servicio Web de Carvajal T&S
 La funcionalidad de pruebas le permite conectarse e interactuar con el
 ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el
 flujo completo y la integración con el Portal Financiero CEN, al cual
-se accede a través de la siguiente liga: `Cenfinanciero <https://cenfinancierolab.cen.biz>`_.
+se accede a través de la siguiente liga: `Cenfinanciero <https://cenflab.cen.biz/site/>`_.
 
 Una vez que el ambiente de producción está listo en Odoo y en Carvajal
 T&S el ambiente de pruebas debe ser deshabilitado para poder enviar la
-información al ambiente de producción de Carvajal, para el cual es
-utilizada la siguiente URL: `Cenfinanciero <https://cenfinancierolab.cen.biz>`_.
+información al ambiente de producción de Carvajal.
 
 
 Configuración de Información para PDF

content/applications/finance/accounting/taxation/taxes/taxcloud.rst

@@ -43,6 +43,52 @@ In Odoo
   and the zip code). Go to :menuselection:`Settings --> Users & Companies --> Companies`
   to open and edit your Company record.
 
+Automatically post taxes to the correct Tax Payable account
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* For each one of your companies that uses TaxCloud, it might be necessary to create a 
+  **User-Defined Default** so that the new taxes generated by the TaxCloud integration are created 
+  with the correct Tax Payable account:
+  
+.. warning::
+   A User-Defined Default impacts all records at creation.  It means that **every** new tax will be 
+   set up to record income in the specified Tax Payable account, unless the tax is manually edited
+   to specify a different income account (or there exists another User-Defined Default that takes 
+   precedence).
+
+* In :menuselection:`Accounting --> Configuration --> Chart of Accounts`, select the Tax Payable
+  account for the company. Take note of the account's ``id`` in the URL string. 
+
+.. image:: taxcloud/user-default-find-account-id.png
+   :alt: The account's ID can be found in the URL string as 'id=...'. 
+   :align: center
+
+* Activate the :ref:`developer mode <developer-mode>`, then go to 
+  :menuselection:`Settings --> Technical --> Actions --> User-Defined Defaults`, and 
+  click on *Create*.
+
+* Click on *Field*, then, in the drop-down menu, on *Search More*. 
+
+.. image:: taxcloud/user-default-search-field.png
+   :alt: Click on 'Search More' in the 'Field' drop-down menu. 
+   :align: center
+
+* In the pop-up's search box, filter on the model ``tax.repartition.line`` and the field ``account``. 
+  Select the ``account`` field of the ``tax.repartition.line`` model. 
+
+.. image:: taxcloud/user-default-select-field.png
+   :alt: Select the 'account' field of the 'tax.repartition.line' model. 
+   :align: center
+
+* In the **Default Value** field, enter the ID of the company's Tax Payable account. 
+  Select the company for which this configuration should apply in the *Company* field. 
+  Click *Save*. 
+
+.. image:: taxcloud/user-default-enter-default-account-id.png
+   :alt: Enter the ID of the company's Tax Payable account. 
+   :align: center
+
+
 How it works
 ============
 

content/applications/sales/sales/ebay_connector/setup.rst

@@ -36,6 +36,117 @@ on **Sync countries and currencies**, then you can fill in all the other fields.
 When all the fields are filled in, you can synchronize the categories and the
 policies by clicking on the adequate buttons.
 
+Accept account deletion notifications
+=====================================
+
+Since September 2021, **eBay requires supporting customer account deletion/closure notifications**.
+As such, when eBay receives an account request for deletion, all eBay partners must confirm the
+reception of the request and take further action if necessary.
+
+Odoo has a notification endpoint to receive those notifications, confirm the reception of the
+request, and handle the first set of actions to anonymize the account details in **Contacts** and
+remove the customer's access to the portal.
+
+.. important::
+   Make sure to correctly :ref:`set up your subscription to the marketplace account deletion
+   notifications <ebay/subscribe-account-deletion-notifications>` as eBay may temporarily disable
+   the related eBay account until the subscription is completed.
+
+Verify your installation of Odoo is up to date
+----------------------------------------------
+
+In order to activate the endpoint, the module **eBay Connector - Account Deletion** must be
+installed. If your Odoo database was first created after September 2021, the module is installed
+automatically and you can proceed to the :ref:`next step <ebay/retrieve-endpoint-details>`.
+
+Update Odoo to the latest release
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The notification endpoint is made available through a new Odoo module; to be able to install it,
+you must make sure that your Odoo source code is up-to-date.
+
+- If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and you can
+  proceed to the next step.
+- If you use Odoo with an on-premise setup or through a partner, then you must update your
+  installation as detailed in :doc:`this documentation page </administration/maintain/update>` or by
+  contacting your integrating partner.
+
+Update the list of available modules
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New modules must be *discovered* by your Odoo instance to be available in the :menuselection:`Apps`
+menu.
+
+To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps ->
+Update Apps List`. A wizard will ask for confirmation.
+
+Install the eBay Connector - Account Deletion update
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. warning::
+   You should never install new modules in your production database without testing them in a
+   duplicate or staging environment. For Odoo.com customers, a duplicate database can be created
+   from the database management page. For Odoo.sh users, you should use a staging or duplicate
+   database. For on-premise users, you should use a staging environment - you should contact your
+   integrating partner for more information regarding how to test a new module in your particular
+   setup.
+
+To install the module, go to the :menuselection:`Apps` menu, remove the `Apps` search facet and
+search for `ebay`. If the module **eBay Connector - Account Deletion** is present and marked as
+installed, your Odoo database is already up-to-date and you can proceed with the next step. If it is
+not yet installed, install it now.
+
+.. _ebay/retrieve-endpoint-details:
+
+Retrieve endpoint details from Odoo
+-----------------------------------
+
+The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`.
+Click on *Generate Token* to retrieve your **Verification Token**.
+
+.. image:: media/verification-token.png
+   :align: center
+   :alt: Button to generate an eBay verification token in Odoo
+
+.. _ebay/subscribe-account-deletion-notifications:
+
+Subscribe to account deletion notifications
+-------------------------------------------
+
+Log in on the `developer portal of eBay <https://go.developer.ebay.com/>`_ and go to **Alerts &
+Notifications**.
+
+.. image:: media/ebay-your-account.png
+   :align: center
+   :alt: Overview of the Alerts & Notifications dashboard of eBay
+
+To subscribe to deletion/closure notifications, eBay needs a few details:
+
+- An **email address** to send notifications to if the endpoint is unreachable.
+- The **endpoint details**:
+
+  - The URL to Odoo's account deletion notification endpoint
+  - A verification token
+
+.. image:: media/ebay-notification-endpoint.png
+   :align: center
+   :alt: Dedicated fields to enter the endpoint details
+
+.. tip::
+   You can edit the last two fields once the email address field is filled out.
+
+Verify the connectivity with the endpoint
+-----------------------------------------
+
+After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity
+with the **Send Test Notification** button.
+
+You should get the following confirmation message: "A test notification was sent successfully!"
+
+.. image:: media/test-notification.png
+   :align: center
+   :alt: Button to send test notification
+
 Using the updated synchronisation method
 ========================================
 
@@ -51,7 +162,9 @@ To switch to the new synchronization mechanism:
 #. Activate the :ref:`developer mode <developer-mode>`.
 #. Go to :menuselection:`Settings --> Technical --> Scheduled Actions`
 #. Archive the old synchronization actions (both are named *Ebay: update product status*)
-#. Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)
+#. Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by
+   default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a
+   day per default)
 #. Ensure that the **Next Execution Date** for both these actions are in the near future
 
 Starting with the next execution date, the new method will be used instead of the old one.

content/applications/sales/subscriptions.rst

@@ -12,7 +12,7 @@ keep the churn under control and have reporting on the main KPIs: MRR, ARR, rete
 upselling, etc.
 
 .. seealso::
-   - `Odoo Tutorials: Subscriptions <https://www.odoo.com/slides/subscription-28>`_
+   - `Odoo Tutorials: Subscriptions <https://www.odoo.com/slides/subscription-20>`_
 
 .. toctree::
    :titlesonly:

content/applications/websites/website/publish/domain_name.rst

@@ -77,7 +77,7 @@ We can now apply the redirection from your domain name's manager account:
 
 .. note:: Here are some specific guidelines to create a CNAME record:
 
-   - `GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__
+   - `GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`__
    - `Namecheap <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-can-i-set-up-a-cname-record-for-my-domain>`__
    - `OVH <https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__
 

content/applications/websites/website/publish/translate.rst

@@ -20,6 +20,12 @@ to the **App** module and Install **Automated translations through Gengo
 Api** and **Website Gengo Translator**. If you want to do it manually,
 don't install anything, and follow the next step.
 
+.. warning::
+    Gengo won't work on Odoo Online and not by default on Odoo.sh. The required
+    Python library `gengo` isn't installed on those platforms. It can be used
+    either on-premise or by adding `gengo` to `requirements.txt` in your
+    Odoo.sh git project.
+
 Now go to your website. On the bottom right corner of the page, click on
 **Add a language**.
 

content/contributing/documentation.rst

@@ -70,12 +70,8 @@ Use the GitHub interface
 #. Verify that you are browsing the documentation in the version that you intend to change. The
    version can be selected from the dropdown in the top menu.
 
-   .. image:: documentation/version-selector.png
-
 #. Head over to the page that you want to change and click on the **Edit on GitHub** button in the
-   bottom of the left menu.
-
-   .. image:: documentation/edit-on-github.png
+   top right corner of the page.
 
 #. If you do not have edit rights on the repository (`odoo/documentation
    <https://github.com/odoo/documentation>`_), you need to fork it by clicking on the appropriate

content/contributing/documentation/rst_cheat_sheet.rst

@@ -520,7 +520,7 @@ Document metadata
 +-----------------+--------------------------------------------------------------------------------+
 | `code-column`   |  | Show a dynamic side column that can be used to display interactive          |
 |                 |    tutorials or code excerpts.                                                 |
-|                 |  | For example, see :doc:`/developer/misc/api/upgrade` or                      |
+|                 |  | For example, see                                                            |
 |                 |    :doc:`/applications/finance/accounting/getting_started/memento`.            |
 +-----------------+--------------------------------------------------------------------------------+
 | `hide-page-toc` | Hide the "On this page" sidebar and use full page width for the content.       |

content/developer/misc/api.rst

@@ -9,4 +9,3 @@ API
 
     api/odoo
     api/iap
-    api/upgrade

content/developer/misc/api/upgrade.rst

@@ -1,655 +0,0 @@
-:code-column:
-
-.. _reference/upgrade-api:
-
-================
-Database Upgrade
-================
-
-Introduction
-~~~~~~~~~~~~
-
-This document describes the API used to upgrade an Odoo database to a
-higher version.
-
-It allows a database to be upgraded without ressorting to the html form at
-https://upgrade.odoo.com
-Although the database will follow the same process described on that form.
-
-
-The required steps are:
-
-* :ref:`creating a request <upgrade-api-create-method>`
-* :ref:`uploading a database dump <upgrade-api-upload-method>`
-* :ref:`running the upgrade process <upgrade-api-process-method>`
-* :ref:`obtaining the status of the database request <upgrade-api-status-method>`
-* :ref:`downloading the upgraded database dump <upgrade-api-download-method>`
-
-The methods
-~~~~~~~~~~~
-
-.. _upgrade-api-create-method:
-
-Creating a database upgrade request
-===================================
-
-This action creates a database request with the following information:
-
-* your contract reference
-* your email address
-* the target version (the Odoo version you want to upgrade to)
-* the purpose of your request (test or production)
-* the database dump name (required but purely informative)
-* optionally the server timezone (for Odoo source version < 6.1)
-
-The ``create`` method
----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/create
-
-    Creates a database upgrade request
-
-    :param str contract: (required) your enterprise contract reference
-    :param str email: (required) your email address
-    :param str target: (required) the Odoo version you want to upgrade to. Valid choices: 11.0, 12.0, 13.0
-    :param str aim: (required) the purpose of your upgrade database request. Valid choices: test, production.
-    :param str filename: (required) a purely informative name for you database dump file
-    :param str timezone: (optional) the timezone used by your server. Only for Odoo source version < 6.1
-    :return: request result
-    :rtype: JSON dictionary
-
-The *create* method returns a JSON dictionary containing the following keys:
-
-.. _upgrade-api-json-failure:
-
-``failures``
-''''''''''''
-
-The list of errors.
-
-A list of dictionaries, each dictionary giving information about one particular
-error. Each dictionary can contain various keys depending of the type of error
-but you will always get the ``reason`` and the ``message`` keys:
-
-* ``reason``: the error type
-* ``message``: a human friendly message
-
-Some possible keys:
-
-* ``code``: a faulty value
-* ``value``: a faulty value
-* ``expected``: a list of valid values
-
-See a sample output aside.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: json
-
-            {
-              "failures": [
-                {
-                  "expected": [
-                    "11.0",
-                    "12.0",
-                    "13.0",
-                  ],
-                  "message": "Invalid value \"5.0\"",
-                  "reason": "TARGET:INVALID",
-                  "value": "5.0"
-                },
-                {
-                  "code": "M123456-abcxyz",
-                  "message": "Can not find contract M123456-abcxyz",
-                  "reason": "CONTRACT:NOT_FOUND"
-                }
-              ]
-            }
-
-
-``request``
-'''''''''''
-
-If the *create* method is successful, the value associated to the *request* key
-will be a dictionary containing various information about the created request:
-
-The most important keys are:
-
-* ``id``: the request id
-* ``key``: your private key for this request
-
-These 2 values will be requested by the other methods (upload, process and status)
-
-The other keys will be explained in the section describing the :ref:`status method <upgrade-api-status-method>`.
-
-
-Sample script
-'''''''''''''
-
-Here are 2 examples of database upgrade request creation using:
-
-* one in the python programming language using the requests library
-* one in the bash programming language using `curl <https://curl.haxx.se>`_ (tool
-  for transferring data using http) and `jq <https://stedolan.github.io/jq>`_ (JSON processor):
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        CREATE_URL = "https://upgrade.odoo.com/database/v1/create"
-        CONTRACT = "M123456-abcdef"
-        AIM = "test"
-        TARGET = "12.0"
-        EMAIL = "john.doe@example.com"
-        FILENAME = "db_name.dump"
-
-        fields = dict([
-            ('aim', AIM),
-            ('email', EMAIL),
-            ('filename', DB_SOURCE),
-            ('contract', CONTRACT),
-            ('target', TARGET),
-        ])
-
-        r = requests.get(CREATE_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        CONTRACT=M123456-abcdef
-        AIM=test
-        TARGET=12.0
-        EMAIL=john.doe@example.com
-        FILENAME=db_name.dump
-        CREATE_URL="https://upgrade.odoo.com/database/v1/create"
-        URL_PARAMS="contract=${CONTRACT}&aim=${AIM}&target=${TARGET}&email=${EMAIL}&filename=${FILENAME}"
-        curl -sS "${CREATE_URL}?${URL_PARAMS}" > create_result.json
-
-        # check for failures
-        failures=$(cat create_result.json | jq -r '.failures[]')
-        if [ "$failures" != "" ]; then
-          echo $failures | jq -r '.'
-          exit 1
-        fi
-
-.. _upgrade-api-upload-method:
-
-Uploading your database dump
-============================
-
-There are 2 methods to upload your database dump:
-
-* the ``upload`` method using the HTTPS protocol
-* the ``request_sftp_access`` method using the SFTP protocol
-
-The ``upload`` method
----------------------
-
-It's the most simple and most straightforward way of uploading your database dump.
-It uses the HTTPS protocol.
-
-.. py:function:: https://upgrade.odoo.com/database/v1/upload
-
-    Uploads a database dump
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        UPLOAD_URL = "https://upgrade.odoo.com/database/v1/upload"
-        DUMPFILE = "/tmp/dump.sql"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-        headers = {"Content-Type": "application/octet-stream"}
-
-        with open(DUMPFILE, 'rb') as f:
-            requests.post(UPLOAD_URL, data=f, params=fields, headers=headers)
-
-    .. code-block:: bash
-
-        UPLOAD_URL="https://upgrade.odoo.com/database/v1/upload"
-        DUMPFILE="openchs.70.cdump"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        HEADER="Content-Type: application/octet-stream"
-        curl -H $HEADER --data-binary "@${DUMPFILE}" "${UPLOAD_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-request-sftp-access-method:
-
-The ``request_sftp_access`` method
-----------------------------------
-
-This method is recommended for big database dumps.
-It uses the SFTP protocol and supports resuming.
-
-It will create a temporary SFTP server where you can connect to and allow you
-to upload your database dump using an SFTP client.
-
-.. py:function:: https://upgrade.odoo.com/database/v1/request_sftp_access
-
-    Creates an SFTP server
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :param str ssh_keys: (required) the path to a file listing the ssh public keys you'd like to use
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The file listing your ssh public keys should be roughly similar to a standard ``authorized_keys`` file.
-This file should only contains public keys, blank lines or comments (lines starting with the ``#`` character)
-
-Your database upgrade request should be in the ``draft`` state.
-
-The ``request_sftp_access`` method returns a JSON dictionary containing the following keys:
-
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        UPLOAD_URL = "https://upgrade.odoo.com/database/v1/request_sftp_access"
-        SSH_KEY = "$HOME/.ssh/id_rsa.pub"
-        SSH_KEY_CONTENT = open(SSH_KEY,'r').read()
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-            ('ssh_keys', SSH_KEY_CONTENT)
-        ])
-
-        r = requests.post(UPLOAD_URL, params=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        REQUEST_SFTP_ACCESS_URL="https://upgrade.odoo.com/database/v1/request_sftp_access"
-        SSH_KEYS=/path/to/your/authorized_keys
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-
-        curl -sS "${REQUEST_SFTP_ACCESS_URL}?${URL_PARAMS}" -F ssh_keys=@${SSH_KEYS} > request_sftp_result.json
-
-        # check for failures
-        failures=$(cat request_sftp_result.json | jq -r '.failures[]')
-        if [ "$failures" != "" ]; then
-          echo $failures | jq -r '.'
-          exit 1
-        fi
-
-
-``failures``
-''''''''''''
-
-The list of errors. See :ref:`failures <upgrade-api-json-failure>` for an
-explanation about the JSON dictionary returned in case of failure.
-
-``request``
-'''''''''''
-
-If the call is successful, the value associated to the *request* key
-will be a dictionary containing your SFTP connection parameters:
-
-* ``hostname``: the host address to connect to
-* ``sftp_port``: the port to connect to
-* ``sftp_user``: the SFTP user to use for connecting
-* ``shared_file``: the filename you need to use (identical to the ``filename`` value you have used when creating the request in the :ref:`create method <upgrade-api-create-method>`.)
-* ``request_id``: the related upgrade request id (only informative, ,not required for the connection)
-* ``sample_command``: a sample command using the 'sftp' client
-
-You should normally be able to connect using the sample command as is.
-
-You will only have access to the ``shared_file``. No other files will be
-accessible and you will not be able to create new files in your shared
-environment on the SFTP server.
-
-Using the 'sftp' client
-+++++++++++++++++++++++
-
-Once you have successfully connected using your SFTP client, you can upload
-your database dump. Here is a sample session using the 'sftp' client:
-
-::
-
-    $ sftp -P 2200 user_10534@upgrade.odoo.com
-    Connected to upgrade.odoo.com.
-    sftp> put /path/to/openchs.70.cdump openchs.70.cdump
-    Uploading /path/to/openchs.70.cdump to /openchs.70.cdump
-    sftp> ls -l openchs.70.cdump
-    -rw-rw-rw-    0 0        0          849920 Aug 30 15:58 openchs.70.cdump
-
-If your connection is interrupted, you can continue your file transfer using
-the ``-a`` command line switch:
-
-.. code-block:: text
-
-    sftp> put -a /path/to/openchs.70.cdump openchs.70.cdump
-    Resuming upload of /path/to/openchs.70.cdump to /openchs.70.cdump
-
-If you don't want to manually type the command and need to automate your
-database upgrade using a script, you can use a batch file or pipe your commands to 'sftp':
-
-::
-
-  echo "put /path/to/openchs.70.cdump openchs.70.cdump" | sftp -b - -P 2200 user_10534@upgrade.odoo.com
-
-The ``-b`` parameter takes a filename. If the filename is ``-``, it reads the commands from standard input.
-
-
-.. _upgrade-api-process-method:
-
-Asking to process your request
-==============================
-
-This action ask the Upgrade Platform to process your database dump.
-
-The ``process`` method
-----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/process
-
-    Process a database dump
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/process"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        PROCESS_URL="https://upgrade.odoo.com/database/v1/process"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${PROCESS_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-skip-tests:
-
-
-Asking to skip the tests 
-=========================
-
-This action asks the Upgrade Platform to skip the tests for your request.
-If you don't want Odoo to test and validate the migration, you can bypass the testing stage and directly get the migrated dump.
-
-The ``skip_test`` method
-------------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/skip_test
-
-    Skip the tests, deliver the upgraded dump, and set the state to 'delivered'
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/skip_test"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        PROCESS_URL="https://upgrade.odoo.com/database/v1/skip_test"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${PROCESS_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-status-method:
-
-Obtaining your request status
-=============================
-
-This action ask the status of your database upgrade request.
-
-The ``status`` method
----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/status
-
-    Ask the status of a database upgrade request
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing various information about your
-database upgrade request.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/status"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        STATUS_URL="https://upgrade.odoo.com/database/v1/status"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${STATUS_URL}?${URL_PARAMS}"
-
-Sample output
--------------
-
-The ``request`` key contains various useful information about your request:
-
-``id``
-    the request id
-``key``
-    your private key
-``email``
-    the email address you supplied when creating the request
-``target``
-    the target Odoo version you supplied when creating the request
-``aim``
-    the purpose (test, production) of your database upgrade request you supplied when creating the request
-``filename``
-    the filename you supplied when creating the request
-``timezone``
-    the timezone you supplied when creating the request
-``state``
-    the state of your request
-``issue_stage``
-    the stage of the issue we have create on Odoo main server
-``issue``
-    the id of the issue we have create on Odoo main server
-``status_url``
-    the URL to access your database upgrade request html page
-``notes_url``
-    the URL to get the notes about your database upgrade
-``original_sql_url``
-    the URL used to get your uploaded (not upgraded) database as an SQL stream
-``original_dump_url``
-    the URL used to get your uploaded (not upgraded) database as an archive file
-``upgraded_sql_url``
-    the URL used to get your upgraded database as an SQL stream
-``upgraded_dump_url``
-    the URL used to get your upgraded database as an archive file
-``modules_url``
-    the URL used to get your custom modules
-``filesize``
-    the size of your uploaded database file
-``database_uuid``
-    the Unique ID of your database
-``created_at``
-    the date when you created the request
-``estimated_time``
-    an estimation of the time it takes to upgrade your database
-``processed_at``
-    time when your database upgrade was started
-``elapsed``
-    the time it takes to upgrade your database
-``filestore``
-    your attachments were converted to the filestore
-``customer_message``
-    an important message related to your request
-``database_version``
-    the guessed Odoo version of your uploaded (not upgraded) database
-``postgresql``
-    the guessed Postgresql version of your uploaded (not upgraded) database
-``compressions``
-    the compression methods used by your uploaded database
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: json
-
-        {
-          "failures": [],
-          "request": {
-            "id": 10534,
-            "key": "Aw7pItGVKFuZ_FOR3U8VFQ==",
-            "email": "john.doe@example.com",
-            "target": "12.0",
-            "aim": "test",
-            "filename": "db_name.dump",
-            "timezone": null,
-            "state": "draft",
-            "issue_stage": "new",
-            "issue": 648398,
-            "status_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/status",
-            "notes_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/notes",
-            "original_sql_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/original/sql",
-            "original_dump_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/original/archive",
-            "upgraded_sql_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/sql",
-            "upgraded_dump_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/archive",
-            "modules_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/modules/archive",
-            "filesize": "912.99 Kb",
-            "database_uuid": null,
-            "created_at": "2018-09-09 07:13:49",
-            "estimated_time": null,
-            "processed_at": null,
-            "elapsed": "00:00",
-            "filestore": false,
-            "customer_message": null,
-            "database_version": null,
-            "postgresql": "9.4",
-            "compressions": [
-              "pgdmp_custom",
-              "sql"
-            ]
-          }
-        }
-
-.. _upgrade-api-download-method:
-
-Downloading your database dump
-==============================
-
-Beside downloading your migrated database using the URL provided by the
-:ref:`status method <upgrade-api-status-method>`, you can also use the SFTP
-protocol as described in the :ref:`request_sftp_access method
-<upgrade-api-request-sftp-access-method>`
-
-The difference is that you'll only be able to download the migrated database. No
-uploading will be possible.
-
-Your database upgrade request should be in the ``done`` state.
-
-Once you have successfully connected using your SFTP client, you can download
-your database dump. Here is a sample session using the 'sftp' client:
-
-::
-
-    $ sftp -P 2200 user_10534@upgrade.odoo.com
-    Connected to upgrade.odoo.com.
-    sftp> get upgraded_openchs.70.cdump /path/to/upgraded_openchs.70.cdump
-    Downloading /upgraded_openchs.70.cdump to /path/to/upgraded_openchs.70.cdump
-

content/developer/reference/addons/testing.rst

@@ -115,13 +115,15 @@ Subclasses of :class:`odoo.tests.common.BaseCase` (usually through
 :class:`~odoo.tests.common.TransactionCase`,
 :class:`~odoo.tests.common.SavepointCase` or
 :class:`~odoo.tests.common.HttpCase`) are automatically tagged with
-``standard``, ``at_install`` and their source module's name by default.
+``standard`` and ``at_install`` by default.
 
 Invocation
 ^^^^^^^^^^
 
 :option:`--test-tags <odoo-bin --test-tags>` can be used to select/filter tests
-to run on the command-line.
+to run on the command-line. It implies :option:`--test-enable <odoo-bin --test-enable>`,
+so it's not necessary to specify :option:`--test-enable <odoo-bin --test-enable>`
+when using :option:`--test-tags <odoo-bin --test-tags>`.
 
 This option defaults to ``+standard`` meaning tests tagged ``standard``
 (explicitly or implicitly) will be run by default when starting Odoo
@@ -152,7 +154,7 @@ have to be selected explicitly:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags nice
+    $ odoo-bin --test-tags nice
 
 Note that only the tests tagged ``nice`` are going to be executed. To run
 *both* ``nice`` and ``standard`` tests, provide multiple values to
@@ -161,10 +163,10 @@ are *additive* (you're selecting all tests with *any* of the specified tags)
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags nice,standard
+    $ odoo-bin --test-tags nice,standard
 
 The config switch parameter also accepts the ``+`` and ``-`` prefixes. The
-``+`` prefix is implied and therefore, totaly optional. The ``-`` (minus)
+``+`` prefix is implied and therefore, totally optional. The ``-`` (minus)
 prefix is made to deselect tests tagged with the prefixed tags, even if they
 are selected by other specified tags e.g. if there are ``standard`` tests which
 are also tagged as ``slow`` you can run all standard tests *except* the slow
@@ -172,7 +174,7 @@ ones:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags 'standard,-slow'
+    $ odoo-bin --test-tags 'standard,-slow'
 
 When you write a test that does not inherit from the
 :class:`~odoo.tests.common.BaseCase`, this test will not have the default tags,
@@ -189,6 +191,36 @@ they're not going to get run:
     class SmallTest(unittest.TestCase):
         ...
 
+Besides tags you can also specify specific modules, classes or functions to
+test. The full syntax of the format accepted by :option:`--test-tags <odoo-bin --test-tags>`
+is:
+
+.. code-block::
+
+    [-][tag][/module][:class][.method]
+
+So if you want to test the `stock_account` module, you can use:
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags /stock_account
+
+If you want to test a specific function with a unique name, it can be specified
+directly:
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags .test_supplier_invoice_forwarded_by_internal_user_without_supplier
+
+This is equivalent to
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags /account:TestAccountIncomingSupplierInvoice.test_supplier_invoice_forwarded_by_internal_user_without_supplier
+
+if the name of the test is unambiguous. Multiple modules, classes and functions
+can be specified at once separated by a `,` like with regular tags.
+
 Special tags
 ^^^^^^^^^^^^
 
@@ -206,43 +238,36 @@ Special tags
   Note that this is *not exclusive* with ``at_install``, however since you
   will generally not want both ``post_install`` is usually paired with
   ``-at_install`` when tagging a test class.
-- *module_name*: Odoo tests classes extending
-  :class:`~odoo.tests.common.BaseCase` are implicitly tagged with the
-  technical name of their module. This allows easily selecting or excluding
-  specific modules when testing e.g. if you want to only run tests from
-  ``stock_account``:
-
-  .. code-block:: console
-
-      $ odoo-bin --test-enable --test-tags stock_account
 
 Examples
 ^^^^^^^^
 
 .. important::
 
-    Tests will be executed only in the installed or updated modules.  So
-    modules have to be selected with the :option:`-u <odoo-bin -u>` or
-    :option:`-i <odoo-bin -i>` switches.  For simplicity, those switches are
+    Tests will be executed only in installed modules. If you're starting from
+    a clean database, you'll need to install the modules with the
+    :option:`-i <odoo-bin -i>` switch at least once. After that it's no longer
+    needed, unless you need to upgrade the module, in which case
+    :option:`-u <odoo-bin -u>` can be used. For simplicity, those switches are
     not specified in the examples below.
 
 Run only the tests from the sale module:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags sale
+    $ odoo-bin --test-tags /sale
 
 Run the tests from the sale module but not the ones tagged as slow:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags 'sale,-slow'
+    $ odoo-bin --test-tags '/sale,-slow'
 
 Run only the tests from stock or tagged as slow:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags '-standard, slow, stock'
+    $ odoo-bin --test-tags '-standard, slow, /stock'
 
 .. note:: ``-standard`` is implicit (not required), and present for clarity
 

content/developer/reference/javascript/qweb.rst

@@ -557,7 +557,7 @@ The javascript QWeb implementation provides a few debugging hooks:
     triggers a debugger breakpoint during template rendering::
 
         <t t-if="a_test">
-            <t t-debug="">
+            <t t-debug=""/>
         </t>
 
     will stop execution if debugging is active (exact condition depend on the

locale/ar/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Dooreen AlMehdar <doa@odoo.com>, 2020\n"
 "Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: ar\n"
 "Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "التطبيقات"

locale/ar/LC_MESSAGES/finance.po

@@ -32,6 +32,7 @@
 # Zuhair Hammadi <zuhair12@gmail.com>, 2021
 # Shaima Safar <shaima.safar@open-inside.com>, 2021
 # Dooreen AlMehdar <doa@odoo.com>, 2021
+# Mohamed Abuelmagd <mabuelmagd12@gmail.com>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -40,7 +41,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:39+0000\n"
-"Last-Translator: Dooreen AlMehdar <doa@odoo.com>, 2021\n"
+"Last-Translator: Mohamed Abuelmagd <mabuelmagd12@gmail.com>, 2021\n"
 "Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -9636,7 +9637,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/getting_started/memento.rst:166
 msgid "30"
-msgstr ""
+msgstr "30"
 
 #: ../../content/applications/finance/accounting/getting_started/memento.rst:168
 msgid "Payment 2"
@@ -9993,7 +9994,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:111
 msgid "15"
-msgstr ""
+msgstr "15"
 
 #: ../../content/applications/finance/accounting/getting_started/process_overview/customer_invoice.rst:117
 msgid "Payment"
@@ -17985,7 +17986,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:89
 msgid "10"
-msgstr ""
+msgstr "10"
 
 #: ../../content/applications/finance/accounting/taxation/taxes/taxes.rst:89
 msgid "1,010.00"

locale/ar/LC_MESSAGES/index.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,6 @@ msgstr ""
 "Language: ar\n"
 "Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr ""

locale/de/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Johannes Croe <jcr@odoo.com>, 2019\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Applications"

locale/de/LC_MESSAGES/index.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,6 @@ msgstr ""
 "Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr ""

locale/es/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Martin Trigaux, 2020\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: es\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Solicitudes"

locale/es/LC_MESSAGES/index.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: jabelchi, 2021\n"
 "Language-Team: Spanish (https://www.transifex.com/odoo/teams/41243/es/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: es\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr "Documentación Odoo"

locale/fr/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Richard Mathot <rim@odoo.com>, 2019\n"
 "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: fr\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Applications"

locale/fr/LC_MESSAGES/general.po

@@ -20,6 +20,8 @@
 # Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2021
 # Fernanda Marques <fem@odoo.com>, 2021
 # Jonathan Castillo <jcs@odoo.com>, 2021
+# Gwladys Jouble <g.jouble@vieconnect.io>, 2021
+# Vallen Delobel <edv@odoo.com>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -28,7 +30,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
-"Last-Translator: Jonathan Castillo <jcs@odoo.com>, 2021\n"
+"Last-Translator: Vallen Delobel <edv@odoo.com>, 2021\n"
 "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -294,13 +296,15 @@ msgstr ""
 
 #: ../../content/applications/general.rst:147
 msgid "Activate the developer mode (debug mode)"
-msgstr ""
+msgstr "Activer le mode développeur (mode débogage)"
 
 #: ../../content/applications/general.rst:149
 msgid ""
 "The developer mode (or debug mode) gives you access to extra and advanced "
 "tools."
 msgstr ""
+"Le mode développeur (ou mode débogage) vous donne accès à des outils "
+"supplémentaires ou avancés."
 
 #: ../../content/applications/general.rst:152
 msgid "Through the Settings application"
@@ -313,23 +317,27 @@ msgstr ""
 
 #: ../../content/applications/general.rstNone
 msgid "Overview of the debug options under settings in Odoo"
-msgstr ""
+msgstr "Aperçu des options de débogage dans les paramètres d'Odoo"
 
 #: ../../content/applications/general.rst:161
 msgid ""
 "*Activate the developer mode (with assets)* is used by developers; *Activate"
 " the developer mode (with tests assets)* is used by developers and testers."
 msgstr ""
+"*Activez le mode développeur (avec les actifs)* est utilisé par les "
+"développeurs; *Activez le mode développeur (avec les actifs tests)* est "
+"utilisé par les développeurs et les testeurs."
 
 #: ../../content/applications/general.rst:164
 msgid ""
 "Once activated, the *Deactivate the developer mode* option becomes "
 "available."
 msgstr ""
+"Une fois activée, l'option *Désactivez le mode développeur\" est disponible."
 
 #: ../../content/applications/general.rst:167
 msgid "Through a browser extension"
-msgstr ""
+msgstr "Via une extension de navigateur"
 
 #: ../../content/applications/general.rst:170
 msgid ""
@@ -347,10 +355,13 @@ msgid ""
 "the mode, while a double click enables it with assets. To deactivate it, use"
 " a single click."
 msgstr ""
+"Pour l'extension *Débogage d'Odoo*, un simple clic permet d'accéder à une "
+"version normale du mode, tandis qu'un double clic l'autorise avec des "
+"actifs. Pour le désactiver, utilisez un simple clic."
 
 #: ../../content/applications/general.rstNone
 msgid "View of odoo’s debug icon in a chrome’s toolbar"
-msgstr ""
+msgstr "Vue de l'icône de débogage d'Odoo dans une barre d'outils de Chrome"
 
 #: ../../content/applications/general.rst:179
 msgid "Through the URL"
@@ -3459,7 +3470,7 @@ msgstr ""
 
 #: ../../content/applications/general/users.rst:73
 msgid "Reset passwords"
-msgstr ""
+msgstr "Réinitialiser les mots de passe"
 
 #: ../../content/applications/general/users.rst:78
 msgid "Enable password resets from login page"
@@ -3468,6 +3479,8 @@ msgstr ""
 #: ../../content/applications/general/users.rst:80
 msgid "It is possible to enable password resets directly from the login page."
 msgstr ""
+"Il est possible d'activer la réinitialisation de mot de passe directement à "
+"partir de la page de connexion. "
 
 #: ../../content/applications/general/users.rst:82
 msgid ""
@@ -3481,7 +3494,7 @@ msgstr ""
 
 #: ../../content/applications/general/users.rst:91
 msgid "Send reset instructions to users"
-msgstr ""
+msgstr "Envoyez les instructions de réinitialisation aux utilisateurs"
 
 #: ../../content/applications/general/users.rst:93
 msgid ""
@@ -3781,7 +3794,7 @@ msgstr ""
 
 #: ../../content/applications/general/users/language.rst:61
 msgid ":doc:`../../websites/website/publish/translate`"
-msgstr ""
+msgstr ":doc:`../../websites/website/publish/translate`"
 
 #: ../../content/applications/general/voip.rst:5
 msgid "VoIP (Voice over Internet Protocol)"

locale/fr/LC_MESSAGES/inventory_and_mrp.po

@@ -22,13 +22,14 @@
 # Stéphane GUILLY <stephane.guilly@laposte.net>, 2021
 # Katerina Katapodi <katerinakatapodi@gmail.com>, 2021
 # Shark McGnark <peculiarcheese@gmail.com>, 2021
-# Thomas Deleval <thd@odoo.com>, 2021
 # Fabien Pinckaers <fp@openerp.com>, 2021
 # Alain Prasquier <aprasquier@odm-tech.com>, 2021
 # Melanie Bernard <mbe@odoo.com>, 2021
 # Jérôme Tanché <jerome.tanche@ouest-dsi.fr>, 2021
 # Fernanda Marques <fem@odoo.com>, 2021
 # Martin Trigaux, 2021
+# Vallen Delobel <edv@odoo.com>, 2021
+# Thomas Deleval <thd@odoo.com>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -37,7 +38,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:39+0000\n"
-"Last-Translator: Martin Trigaux, 2021\n"
+"Last-Translator: Thomas Deleval <thd@odoo.com>, 2021\n"
 "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -3583,7 +3584,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:28
 msgid "Receive the vendor bill"
-msgstr ""
+msgstr "Recevoir la facture fournisseur"
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs.rst:30
 msgid ""
@@ -4031,7 +4032,7 @@ msgstr "4,68"
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:215
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:288
 msgid "Liabilities: Accounts Payable"
-msgstr ""
+msgstr "Passif : Comptes créditeurs"
 
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:215
 #: ../../content/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config.rst:288
@@ -5173,7 +5174,7 @@ msgstr ""
 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:48
 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:45
 msgid "How does it work?"
-msgstr ""
+msgstr "Comment cela fonctionne-t-il?"
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:51
 msgid "Pull Rules"
@@ -5270,7 +5271,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:111
 msgid "Manage default locations per product;"
-msgstr ""
+msgstr "Gérer les emplacements par défaut par produit;"
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst:112
 msgid ""
@@ -6104,7 +6105,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:209
 msgid "09/30/2019"
-msgstr ""
+msgstr "09/30/2019"
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:211
 msgid "0000002"
@@ -6116,7 +6117,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213
 msgid "0000003"
-msgstr ""
+msgstr "0000003"
 
 #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/removal.rst:213
 msgid "10/31/2019"
@@ -7860,7 +7861,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:89
 msgid "**C = A + B + s**"
-msgstr ""
+msgstr "**C = A + B + s**"
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:91
 msgid "With:"
@@ -8153,7 +8154,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48
 msgid "Estimate your demand and launch replenishment"
-msgstr ""
+msgstr "Estimez votre demande et lancez le réapprovisionnement "
 
 #: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:50
 msgid ""
@@ -10608,7 +10609,7 @@ msgstr ""
 
 #: ../../content/applications/inventory_and_mrp/quality/control/control_points.rst:193
 msgid "Print Label"
-msgstr ""
+msgstr "Imprimer l'Etiquette"
 
 #: ../../content/applications/inventory_and_mrp/quality/control/control_points.rst:195
 msgid ""

locale/fr/LC_MESSAGES/marketing.po

@@ -16,6 +16,7 @@
 # Fernanda Marques <fem@odoo.com>, 2021
 # David David <f322p3ph@yahoo.fr>, 2021
 # Gwladys Jouble <g.jouble@vieconnect.io>, 2021
+# Camille Dantinne <cmd@odoo.com>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -24,7 +25,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:39+0000\n"
-"Last-Translator: Gwladys Jouble <g.jouble@vieconnect.io>, 2021\n"
+"Last-Translator: Camille Dantinne <cmd@odoo.com>, 2021\n"
 "Language-Team: French (https://www.transifex.com/odoo/teams/41243/fr/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -558,7 +559,7 @@ msgstr ""
 #: ../../content/applications/marketing/events/overview/create_event.rst:68
 #: ../../content/applications/marketing/survey/overview/create.rst:22
 msgid "Tab: Questions"
-msgstr ""
+msgstr "Onglet : Questions"
 
 #: ../../content/applications/marketing/events/overview/create_event.rst:70
 msgid ""
@@ -894,13 +895,15 @@ msgstr ""
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20
 msgid "A total number of 20 records match the criteria."
-msgstr ""
+msgstr "Au total, 20 enregistrements correspondent aux critères."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:28
 msgid ""
 "Out of those 20 records, 25 have become participants, in other words, they "
 "have matched the criteria."
 msgstr ""
+"Sur ces 20 enregistrements, 25 sont devenus participants, c'est-à-dire "
+"qu'ils ont répondu aux critères."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:36
 msgid ""
@@ -908,12 +911,18 @@ msgid ""
 " look at the *Target* model and check if new records have been added or "
 "modified, keeping the flow up-to-date."
 msgstr ""
+"Chaque fois que le système s'exécute, en mettant à jour les chiffres et en "
+"déclenchant des actions, il examine le modèle *Cible* et vérifie si de "
+"nouveaux enregistrements ont été ajoutés ou modifiés, en gardant le flux à "
+"jour."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41
 msgid ""
 "The filter here is applied to *all* activities. Leads that lose the tag in "
 "the meantime will be excluded from later activities."
 msgstr ""
+"Ici, le filtre est appliqué à *toutes* les activités. Les prospects qui "
+"perdent le tag entre-temps seront exclus des activités ultérieures."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45
 msgid ""
@@ -924,6 +933,14 @@ msgid ""
 "participants before. It will just add new ones. For this reason, the number "
 "of *Records* can be different from the number of *Participants*."
 msgstr ""
+"*Enregistrements* est un nombre en temps réel, par conséquent, pendant que "
+"le flux de travail (workflow) est en cours d'exécution, des modifications "
+"des enregistrements d'opportunités peuvent être apportées - supprimer, "
+"ajouter, ajuster - en mettant à jour le nombre d'enregistrements, mais pas "
+"en modifiant le nombre de participants, car la métrique * n'excluera pas* "
+"les opportunités qui ont été définies comme participants auparavant. Il en "
+"ajoutera juste des nouveaux. Pour cette raison, le nombre "
+"d'*enregistrements* peut être différent du nombre de *Participants*."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
 msgid ""
@@ -932,12 +949,19 @@ msgid ""
 " performed if the records satisfied both filters, the activity and its "
 "domain one."
 msgstr ""
+"Vous pouvez également appliquer des filtres aux activités individuellement, "
+"sous *Domaine*. Une fonctionnalité utile pour spécifier un filtre individuel"
+" qui ne sera effectué que si les enregistrements satisfont aux deux filtres,"
+" l'activité et son domaine."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
 msgid ""
 "Example: for an activity sending an SMS, you could make sure a phone number "
 "is set to avoid triggering a SMS that would never be sent and crash."
 msgstr ""
+"Exemple : pour une activité d'envoi de SMS, vous pouvez vous assurer qu'un "
+"numéro de téléphone est défini pour éviter de déclencher un SMS qui ne "
+"serait jamais envoyé et qui planterait."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64
 msgid ""
@@ -945,18 +969,25 @@ msgid ""
 " the filter(s) of that activity - was performed successfully in relation to "
 "the total number of participants."
 msgstr ""
+"*Réussies* est le nombre de fois où la recherche de participants - qui "
+"correspondent au(x) filtre(s) de cette activité - a été effectuée avec "
+"succès par rapport au nombre total de participants."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:65
 msgid ""
 "If a participant does not match the conditions, it will be added to "
 "*Rejected*."
 msgstr ""
+"Si un participant ne correspond pas aux conditions, il sera ajouté à "
+"*Refusées*."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71
 msgid ""
 "Hovering over the graph, you can see the number of successful and rejected "
 "participants, per day, for the last 15 days."
 msgstr ""
+"En survolant le graphique, vous pouvez voir le nombre de participants qui "
+"ont réussis et qui sont rejetés, par jour, au cours des 15 derniers jours."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75
 msgid ""
@@ -964,6 +995,9 @@ msgid ""
 "automatically added to the workflow, and, it will start the workflow from "
 "the beginning (parent action)."
 msgstr ""
+"Chaque fois qu'un nouvel enregistrement est ajouté au modèle *Cible*, il "
+"sera automatiquement ajouté au flux de travail et démarrera le flux de "
+"travail depuis le début (action parente)."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79
 msgid ":doc:`../overview/automate_actions`"
@@ -1563,7 +1597,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing.rst:5
 msgid "Pricing and FAQ"
-msgstr ""
+msgstr "Tarification et FAQ"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:3
 msgid "SMS Pricing and FAQ"
@@ -1571,27 +1605,31 @@ msgstr "Tarification SMS et FAQ"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:6
 msgid "What do I need to send SMSs?"
-msgstr ""
+msgstr "De quoi ai-je besoin pour envoyer des SMS ?"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:7
 msgid ""
 "SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
 "prepaid credits* to work."
 msgstr ""
+"La messagerie texte SMS est un service d'achat intégré (IAP) qui * nécessite"
+" des crédits prépayés * pour fonctionner."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:11
 msgid "How many types of SMSs are there?"
-msgstr ""
+msgstr "Combien de types de SMS existe-t-il ?"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:12
 msgid "There are 2 types: GSM7 and UNICODE."
-msgstr ""
+msgstr "Il y a 2 types : GSM7 et UNICODE."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:14
 msgid ""
 "**GSM7** is the standard format, with a limit of 160 characters per message,"
 " that includes the following characters:"
 msgstr ""
+"**GSM7** est le format standard, avec une limite de 160 caractères par "
+"message, qui comprend les caractères suivants :"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
 msgid "GSM7 in Odoo SMS Marketing"
@@ -1602,6 +1640,8 @@ msgid ""
 "**UNICODE** is the format applied if a special character, that *is not* in "
 "the GSM7 list, is used. Limit per SMS: 70 characters."
 msgstr ""
+"**UNICODE** est le format appliqué si un caractère spécial, qui *n'est pas* "
+"dans la liste GSM7, est utilisé. Limite par SMS : 70 caractères."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:27
 msgid ""
@@ -1611,28 +1651,39 @@ msgid ""
 "system will inform you in real-time about the number of SMS your message "
 "represents."
 msgstr ""
+"Pour GSM7 SMS, la limite de taille est de 160 caractères et pour Unicode de "
+"70. *Au-dessus de ces limites, le contenu est divisé en un message en "
+"plusieurs parties* et la limite de caractères est abaissée à 153 pour GSM7 "
+"et à 67 pour Unicode. Le système vous informera en temps réel du nombre de "
+"SMS que représente votre message."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:34
 msgid "How much does it cost to send an SMS?"
-msgstr ""
+msgstr "Combien coûte l'envoi d'un SMS ?"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:35
 msgid ""
 "The price of an SMS depends on the destination and the length (number of "
 "characters) of the message."
 msgstr ""
+"Le prix d'un SMS dépend de la destination et de la longueur (nombre de "
+"caractères) du message."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37
 msgid ""
 "To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
 "://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
 msgstr ""
+"Pour voir le **prix par pays, veuillez consulter **: `Odoo SMS - FAQ <https"
+"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39
 msgid ""
 "The number of SMSs a message represents will be always available to you in "
 "your database."
 msgstr ""
+"Le nombre de SMS qu'un message représente sera toujours disponible dans "
+"votre base de données."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
@@ -1642,15 +1693,15 @@ msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49
 msgid "How do I buy credits?"
-msgstr ""
+msgstr "Comment acheter des crédits ?"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:50
 msgid "Go to :menuselection:`Settings --> Buy Credits`."
-msgstr ""
+msgstr "Allez dans :menuselection:`Configuration --> Acheter des crédits`."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:57
 msgid "Or go to :menuselection:`Settings --> View my Services`."
-msgstr ""
+msgstr "Ou allez dans :menuselection:`Configuration --> Voir mes services`."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:65
 msgid ""
@@ -1663,7 +1714,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:70
 msgid "More common questions"
-msgstr ""
+msgstr "Questions plus courantes"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:72
 msgid "**Is there an expiration time for my credits?**"
@@ -1671,7 +1722,7 @@ msgstr "**Est-ce que mes crédits expirent-ils?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:74
 msgid "No, credits do not expire."
-msgstr ""
+msgstr "Non, les crédits n'expirent pas."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:77
 msgid ""
@@ -1731,6 +1782,10 @@ msgid ""
 ":ref:`developer mode <developer-mode>` under :menuselection:`Technical --> "
 "SMS`."
 msgstr ""
+"Oui, le SMS est enregistré sous forme de note sous le chatter de "
+"l'enregistrement correspondant, et un historique complet des SMS envoyés est"
+" disponible en  :ref:`developer mode <developer-mode>` sous "
+":menuselection:`Technique --> SMS`."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:106
 msgid "**Can I send as many SMSs I want at once?**"
@@ -1793,10 +1848,12 @@ msgstr "**Comment le règlement RGPD affect-il ce service?**"
 msgid ""
 "Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
 msgstr ""
+"Veuillez trouver notre `Politique de confidentialité ici "
+"<https://iap.odoo.com/privacy#sms>`__."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:131
 msgid "**Can I use my own SMS provider?**"
-msgstr ""
+msgstr "**Puis-je utiliser mon propre fournisseur de SMS ?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:133
 msgid ""
@@ -2216,7 +2273,7 @@ msgstr "Sondage"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:3
 msgid "Get Started with Surveys"
-msgstr ""
+msgstr "Pour commencer avec Surveys"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:5
 msgid ""
@@ -2226,6 +2283,11 @@ msgid ""
 " and satisfied with their work environment, and even to find out what your "
 "market is thinking."
 msgstr ""
+"Les sondages peuvent être utilisés à diverses fins qui peuvent aller de la "
+"collecte des commentaires des clients, évaluer le succès d'un événement, "
+"mesurer le degré de satisfaction des clients avec vos produits/services, "
+"évaluer si les employés sont contents et satisfaits de leur environnement de"
+" travail, et même jusqu'à découvrir ce que pense votre marché."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:13
 msgid ""
@@ -2234,6 +2296,11 @@ msgid ""
 "different applications might use it for different purposes such as "
 "recruitment, certification, or employee appraisal."
 msgstr ""
+"Lors de la création de votre sondage, choisissez un *Titre* et une "
+"*Catégorie*. Le champ *Catégorie* est utilisé pour savoir dans quel contexte"
+" l'enquête est menée, car différentes applications peuvent l'utiliser à "
+"différentes fins telles que le recrutement, la certification ou l'évaluation"
+" des employés."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid ""
@@ -2243,6 +2310,7 @@ msgstr ""
 #: ../../content/applications/marketing/survey/overview/create.rst:24
 msgid "Add sections and questions by clicking on the respective links."
 msgstr ""
+"Ajoutez des sections et des questions en cliquant sur les liens respectifs."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:27
 msgid ""
@@ -2251,18 +2319,27 @@ msgid ""
 "set an *Error message* to be shown when the user tries to submit the survey "
 "without answering the respective question."
 msgstr ""
+"Sur la fiche *Sections et Questions*, une fois le type de question choisi et"
+" la réponse ajoutée, sous l'onglet *Options*, activez *Réponse obligatoire*,"
+" et définissez un *Message d'erreur* à afficher lorsque l'utilisateur essaie"
+" de soumettre le sondage sans répondre à la question correspondante."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:29
 msgid ""
 "Depending on the *Question Type*, the tab *Options* aggregates extra and "
 "different possibilities. Examples:"
 msgstr ""
+"Selon le *Type de question*, l'onglet *Options* regroupe des possibilités "
+"supplémentaires et différentes. Exemples :"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:31
 msgid ""
 "*Single Line Text Box* - can choose a minimum and maximum text length "
 "(number of characters - spaces do not count), and its error message."
 msgstr ""
+"*Plusieurs lignes de champ de texte* - peut choisir une longueur de texte "
+"minimale et maximale (nombre de caractères - les espaces ne comptent pas), "
+"et son message d'erreur."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:33
 msgid ""
@@ -2272,12 +2349,20 @@ msgid ""
 "recorded. Or, enable the comment field to be displayed as an answer choice, "
 "with which a text type field is displayed."
 msgstr ""
+"*Choix multiples : réponses multiples*: cchoisissez entre des boutons radio "
+"ou une liste de menu déroulant, et si vous souhaitez avoir un champ de "
+"commentaire. Si l'utilisateur sélectionne une réponse et tape un "
+"commentaire, les valeurs sont enregistrées séparément. Ou activez "
+"l'affichage du champ de commentaire en tant que choix de réponse, avec "
+"lequel un champ de type texte est affiché."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:37
 msgid ""
 "*Matrix Type*: choose if you would like to have one or multiple choices per "
 "row."
 msgstr ""
+"*Matrice*: choisissez si vous souhaitez avoir un ou plusieurs choix par "
+"ligne."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid "Sections and questions view of a survey in Odoo Surveys"
@@ -2285,13 +2370,15 @@ msgstr ""
 
 #: ../../content/applications/marketing/survey/overview/create.rst:44
 msgid "Tab: Description"
-msgstr ""
+msgstr "Onglet : Description"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:46
 msgid ""
 "Write a *Description* to be displayed under the title of the survey's "
 "homepage."
 msgstr ""
+"Rédigez une *Description* tà afficher sous le titre de la page d'accueil de "
+"l'enquête."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid ""
@@ -2302,10 +2389,12 @@ msgstr ""
 #: ../../content/applications/marketing/survey/overview/create.rst:53
 msgid "Click on *Edit* to personalize your pages with the website builder."
 msgstr ""
+"Cliquez sur *Modifier* pour personnaliser vos pages avec le créateur de site"
+" Web."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:56
 msgid "Tab: Options"
-msgstr ""
+msgstr "Onglet : Options"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:58
 msgid ""
@@ -2313,6 +2402,10 @@ msgid ""
 "*One page per section* or *One page per question*, an option *Back Button* "
 "becomes available, which allows the user to go back pages."
 msgstr ""
+"Sous l'onglet *Options*, choisissez la *Mise en page* de vos questions. Si "
+"vous choisissez *Une page par sectionn* or *Une page par question*, une "
+"option *Bouton Retour* devient disponible, ce qui permet à l'utilisateur de "
+"revenir aux pages précédentes."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid ""
@@ -2322,7 +2415,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/survey/overview/create.rst:67
 msgid "Test and share the survey"
-msgstr ""
+msgstr "Tester et partager le sondage"
 
 #: ../../content/applications/marketing/survey/overview/create.rst:70
 msgid ""
@@ -2330,12 +2423,18 @@ msgid ""
 "errors. As answers get collected, click on *Answers* to access all the "
 "details of the respondent and his answers."
 msgstr ""
+"Une fois que votre sondage est prêt, *testez-le* pour éviter de le "
+"*partager* avec des erreurs potentielles. Au fur et à mesure que les "
+"réponses sont collectées, cliquez sur *Réponses* pour accéder à tous les "
+"détails du répondant et de ses réponses."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:72
 msgid ""
 "By default, a filter *Except Test Entries* is applied to keep the list of "
 "entries clean with only real participants."
 msgstr ""
+"Par défaut, un filtre *Sauf entrées test* est appliqué pour garder la liste "
+"des entrées propre avec uniquement de vrais participants."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid "View list of the participations of a survey in Odoo Surveys"
@@ -2346,10 +2445,14 @@ msgid ""
 "Another way to access detailed answers is by going to "
 ":menuselection:`Participations --> Participations`."
 msgstr ""
+"Une autre façon d'accéder aux réponses détaillées est d'aller dans "
+":menuselection:`Participations --> Participations`."
 
 #: ../../content/applications/marketing/survey/overview/create.rst:80
 msgid "Click on *See results* to be redirected to an analytical page."
 msgstr ""
+"Cliquez sur *Voir les résultats* pour être redirigé vers une page "
+"analytique."
 
 #: ../../content/applications/marketing/survey/overview/create.rstNone
 msgid "View of an analytical page for Odoo Surveys"
@@ -2367,7 +2470,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/survey/overview/scoring.rst:3
 msgid "Scoring Surveys"
-msgstr ""
+msgstr "Noter les sondages"
 
 #: ../../content/applications/marketing/survey/overview/scoring.rst:5
 msgid ""
@@ -2375,6 +2478,10 @@ msgid ""
 " satisfaction, attach points to the answers of specific questions. The "
 "points are summed up to give your respondent a final score."
 msgstr ""
+"Pour mesurer la performance de votre répondant, sa connaissance d'un sujet "
+"ou sa satisfaction globale, attachez des points aux réponses à des questions"
+" spécifiques. Les points sont additionnés pour donner à votre répondant un "
+"score final."
 
 #: ../../content/applications/marketing/survey/overview/scoring.rst:9
 msgid ""
@@ -2383,6 +2490,10 @@ msgid ""
 "without answers at the end*. Now, on your question’s form, set the right "
 "answer and score."
 msgstr ""
+"Sur le formulaire de votre sondage, cliquez sur l'onglet *Options*, "
+"choisissez entre *Notation avec réponses à la fin* ou *Notation sans "
+"réponses à la fin*. Maintenant, sur la fiche de votre question, sous "
+"l'onglet *Réponses*, définissez la bonne réponse et le bon score."
 
 #: ../../content/applications/marketing/survey/overview/scoring.rstNone
 msgid "Form view of a survey showing a list of answers in Odoo Surveys"
@@ -2395,6 +2506,10 @@ msgid ""
 "certification is automatically sent by email to the users who successfully "
 "finish it."
 msgstr ""
+"Définissez le pourcentage de score que l'utilisateur doit atteindre pour "
+"avoir répondu avec succès à l'enquête. Si vous activez *Est une "
+"certification*, choisissez son modèle. La certification est automatiquement "
+"envoyée par email aux utilisateurs qui la terminent avec succès."
 
 #: ../../content/applications/marketing/survey/overview/scoring.rstNone
 msgid ""
@@ -2409,6 +2524,10 @@ msgid ""
 "of the website that access the page *Courses* can also see the granted "
 "badges."
 msgstr ""
+"Activez *Connexion requise* pour pouvoir *Donner des badges*. Les badges "
+"sont liés à la section eLearning de votre site Web. Outre l'utilisateur "
+"connecté, les visiteurs du site Web qui accèdent à la page *Cours* peuvent "
+"également voir les badges accordés."
 
 #: ../../content/applications/marketing/survey/overview/scoring.rstNone
 msgid ""
@@ -2418,7 +2537,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/survey/overview/time_random.rst:3
 msgid "Time and Randomize Questions"
-msgstr ""
+msgstr "Chronométrer et randomiser les questions"
 
 #: ../../content/applications/marketing/survey/overview/time_random.rst:6
 msgid "Time Limit"
@@ -2431,10 +2550,14 @@ msgid ""
 "amount of time to find the answers, or to decrease the chance of having them"
 " looking at external resources."
 msgstr ""
+"Dans les sondages chronométrés, les répondants doivent remplir le sondage "
+"dans un certain laps de temps. Il peut être utilisé pour garantir que tous "
+"les répondants disposent du même temps pour trouver les réponses, ou pour "
+"réduire les chances qu'ils consultent des ressources externes."
 
 #: ../../content/applications/marketing/survey/overview/time_random.rst:11
 msgid "Set the *Time limit* under the tab *Options*."
-msgstr ""
+msgstr "Définissez le *Temps limite du sondage* sous l'onglet *Options*."
 
 #: ../../content/applications/marketing/survey/overview/time_random.rstNone
 msgid ""
@@ -2447,6 +2570,9 @@ msgid ""
 "time. Surveys not \\ submitted by the *Time limit* do not have their answers"
 " saved."
 msgstr ""
+"Une minuterie est affichée sur les pages afin que l'utilisateur puisse "
+"suivre le temps restant. Les sondages non soumis dans le *Délai* n'ont pas "
+"leurs réponses sauvegardées."
 
 #: ../../content/applications/marketing/survey/overview/time_random.rst:21
 msgid "Selection"
@@ -2458,6 +2584,10 @@ msgid ""
 " random order every time someone opens the questionnaire. This can be useful"
 " to avoid having respondents looking at each others' answers."
 msgstr ""
+"Lorsque vous randomisez un sondage, vous permettez aux questions d'être "
+"mélangées dans un ordre aléatoire chaque fois que quelqu'un ouvre le "
+"questionnaire. Cela peut être utile pour éviter que les répondants examinent"
+" les réponses des autres."
 
 #: ../../content/applications/marketing/survey/overview/time_random.rst:27
 msgid ""
@@ -2465,6 +2595,9 @@ msgid ""
 "under the tab *Questions*, set how many of the questions in that section "
 "should be taken into account during the shuffling."
 msgstr ""
+"Pour ce faire, sous l'onglet *Options*, activez *Randomisé par section*. "
+"Maintenant, sous l'onglet *Questions*, définissez combien de questions de "
+"cette section doivent être prises en compte lors du mélange."
 
 #: ../../content/applications/marketing/survey/overview/time_random.rstNone
 msgid ""

locale/nl/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2019\n"
 "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: nl\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Applicaties"

locale/nl/LC_MESSAGES/general.po

@@ -4,13 +4,13 @@
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
-# Erwin van der Ploeg <erwin@odooexperts.nl>, 2020
 # Eric Geens <ericgeens@yahoo.com>, 2020
 # Pol Van Dingenen <pol.vandingenen@vanroey.be>, 2021
 # Maxim Vandenbroucke <mxv@odoo.com>, 2021
 # Martin Trigaux, 2021
 # Yenthe Van Ginneken <yenthespam@gmail.com>, 2021
 # Gunther Clauwaert <gclauwae@hotmail.com>, 2021
+# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -19,7 +19,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
-"Last-Translator: Gunther Clauwaert <gclauwae@hotmail.com>, 2021\n"
+"Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2021\n"
 "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1823,7 +1823,7 @@ msgstr ""
 
 #: ../../content/applications/general/payment_acquirers.rst:47
 msgid "Bank Payments"
-msgstr ""
+msgstr "Bankbetalingen"
 
 #: ../../content/applications/general/payment_acquirers.rst:0
 msgid ":doc:`Wire Transfer <payment_acquirers/wire_transfer>`"
@@ -2207,7 +2207,7 @@ msgstr ""
 
 #: ../../content/applications/general/payment_acquirers/authorize.rst:25
 msgid "API Login ID"
-msgstr ""
+msgstr "API-aanmeldings-ID"
 
 #: ../../content/applications/general/payment_acquirers/authorize.rst:26
 msgid "Transaction Key"

locale/nl/LC_MESSAGES/marketing.po

@@ -5,10 +5,11 @@
 # 
 # Translators:
 # Martin Trigaux, 2021
-# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # Yenthe Van Ginneken <yenthespam@gmail.com>, 2021
 # Eric Geens <ericgeens@yahoo.com>, 2021
 # Gunther Clauwaert <gclauwae@hotmail.com>, 2021
+# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
+# Bert Burggraaf, 2021
 # 
 #, fuzzy
 msgid ""
@@ -17,7 +18,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:39+0000\n"
-"Last-Translator: Gunther Clauwaert <gclauwae@hotmail.com>, 2021\n"
+"Last-Translator: Bert Burggraaf, 2021\n"
 "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -318,7 +319,7 @@ msgstr ""
 
 #: ../../content/applications/marketing/email_marketing/overview/send_emails.rst:85
 msgid ":doc:`/applications/productivity/discuss/advanced/email_servers`"
-msgstr ""
+msgstr ":doc:`/applications/productivity/discuss/advanced/email_servers`"
 
 #: ../../content/applications/marketing/email_marketing/overview/send_emails.rst:86
 #: ../../content/applications/marketing/sms_marketing/overview/integrations_and_template.rst:79
@@ -845,19 +846,23 @@ msgstr "Geavanceerd"
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3
 msgid "Understanding Metrics"
-msgstr ""
+msgstr "Statistieken begrijpen"
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:4
 msgid ""
 "Metrics are values that help you measure progress and can be a powerful way "
 "of linking your employees to goals."
 msgstr ""
+"Statistieken zijn waarden die je helpen de voortgang te meten en kunnen een "
+"krachtige manier zijn om je medewerkers aan doelen te koppelen."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9
 msgid ""
 "When you create a workflow in Odoo, its visual content already shows metrics"
 " in a graph form and in numbers."
 msgstr ""
+"Wanneer je een workflow aanmaakt in Odoo, toont de visuele inhoud ervan al "
+"statistieken in een grafiekvorm en in cijfers."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10
 msgid "Let’s consider the example below:"
@@ -877,6 +882,9 @@ msgid ""
 " to the ones whose *Tag Name* contain the description “Product”, and have an"
 " email address set."
 msgstr ""
+"Het *Target* - zakelijk object - is *Lead/Opportunity* en is beperkt tot "
+"degenen waarvan de *Tag Name* de beschrijving \"Product\" bevat en een "
+"e-mailadres heeft."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20
 msgid "A total number of 20 records match the criteria."
@@ -896,6 +904,9 @@ msgid ""
 " look at the *Target* model and check if new records have been added or "
 "modified, keeping the flow up-to-date."
 msgstr ""
+"Elke keer dat het systeem draait, nummers bijwerkt en acties activeert, "
+"kijkt het naar het *Target*-model en controleert of er nieuwe records zijn "
+"toegevoegd of gewijzigd, waardoor de stroom up-to-date blijft."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41
 msgid ""
@@ -914,6 +925,13 @@ msgid ""
 "participants before. It will just add new ones. For this reason, the number "
 "of *Records* can be different from the number of *Participants*."
 msgstr ""
+"*Records* is een real-time getal, dus terwijl de workflow loopt, kunnen "
+"wijzigingen in opportunityrecords worden aangebracht - verwijderen, "
+"toevoegen, aanpassen - het aantal records bijwerken, maar het aantal "
+"deelnemers niet wijzigen, aangezien de statistiek *zal niet* kansen uitsluit"
+" die eerder als deelnemers zijn ingesteld. Er worden alleen nieuwe "
+"toegevoegd. Om deze reden kan het aantal *Records* verschillen van het "
+"aantal *Deelnemers*."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
 msgid ""
@@ -922,12 +940,19 @@ msgid ""
 " performed if the records satisfied both filters, the activity and its "
 "domain one."
 msgstr ""
+"Je kunt ook filters laten toepassen op activiteiten afzonderlijk, onder "
+"*Domein*. Een handige functie om een afzonderlijk filter op te geven dat "
+"alleen wordt uitgevoerd als de records aan beide filters, de activiteit en "
+"het domein ervan voldoen."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
 msgid ""
 "Example: for an activity sending an SMS, you could make sure a phone number "
 "is set to avoid triggering a SMS that would never be sent and crash."
 msgstr ""
+"Voorbeeld: voor een activiteit die een sms verzendt, kun je ervoor zorgen "
+"dat er een telefoonnummer is ingesteld om te voorkomen dat er een sms wordt "
+"geactiveerd die nooit zou worden verzonden en zou crashen."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64
 msgid ""
@@ -935,6 +960,9 @@ msgid ""
 " the filter(s) of that activity - was performed successfully in relation to "
 "the total number of participants."
 msgstr ""
+"*Succes* is het aantal keren dat het zoeken naar deelnemers - die "
+"overeenkomen met de filter(s) van die activiteit - succesvol is uitgevoerd "
+"in verhouding tot het totaal aantal deelnemers."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:65
 msgid ""
@@ -958,6 +986,9 @@ msgid ""
 "automatically added to the workflow, and, it will start the workflow from "
 "the beginning (parent action)."
 msgstr ""
+"Elke keer dat een nieuw record wordt toegevoegd aan het *Target*-model, "
+"wordt het automatisch toegevoegd aan de workflow en wordt de workflow vanaf "
+"het begin gestart (bovenliggende actie)."
 
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79
 msgid ":doc:`../overview/automate_actions`"
@@ -1650,7 +1681,7 @@ msgstr "Ga naar :menuselection:`Instellingen --> Koop Krediet`."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:57
 msgid "Or go to :menuselection:`Settings --> View my Services`."
-msgstr ""
+msgstr "Of ga naar : menuselectie: `Instellingen --> Bekijk mijn diensten`."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:65
 msgid ""
@@ -1763,34 +1794,41 @@ msgid ""
 "**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
 " ticket for a festival)?**"
 msgstr ""
+"**Wat gebeurt er als ik mijn sms naar een betalend nummer stuur "
+"(bijvoorbeeld: een wedstrijd om een ticket voor een festival te winnen)?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:119
 msgid ""
 "The SMS will not be delivered to that kind of number, so you won’t be "
 "charged."
 msgstr ""
+"De sms wordt niet op dat soort nummer afgeleverd, dus er worden geen kosten "
+"in rekening gebracht."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:122
 msgid ""
 "**Can I identify the numbers that do not exist when I send several SMSs?**"
 msgstr ""
+"**Kan ik de niet-bestaande nummers identificeren als ik meerdere sms'jes "
+"stuur?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:124
 msgid "Only the ones that have an invalid format."
-msgstr ""
+msgstr "Alleen degenen die een ongeldig formaat hebben."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:127
 msgid "**How does the GDPR regulation affect this service?**"
-msgstr ""
+msgstr "**Wat voor invloed heeft de AVG-regelgeving op deze service?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:129
 msgid ""
 "Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
 msgstr ""
+"Hier vind je ons `Privacybeleid <https://iap.odoo.com/privacy#sms>`__."
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:131
 msgid "**Can I use my own SMS provider?**"
-msgstr ""
+msgstr "**Kan ik mijn eigen sms-provider gebruiken?**"
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:133
 msgid ""

locale/nl/LC_MESSAGES/sphinx.po

@@ -5,11 +5,11 @@
 # 
 # Translators:
 # Martin Trigaux, 2021
-# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # Yenthe Van Ginneken <yenthespam@gmail.com>, 2021
 # Nils van Odoo <nvo@odoo.com>, 2021
 # Martien van Geene <martien.vangeene@gmail.com>, 2021
 # Gunther Clauwaert <gclauwae@hotmail.com>, 2021
+# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -18,7 +18,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-06-14 14:06+0000\n"
-"Last-Translator: Gunther Clauwaert <gclauwae@hotmail.com>, 2021\n"
+"Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2021\n"
 "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -115,7 +115,7 @@ msgstr ""
 
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:70
 msgid "Developer"
-msgstr ""
+msgstr "Developer"
 
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:71
 msgid ""

locale/nl/LC_MESSAGES/websites.po

@@ -5,12 +5,12 @@
 # 
 # Translators:
 # Martin Trigaux, 2021
-# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # Yenthe Van Ginneken <yenthespam@gmail.com>, 2021
 # Eric Geens <ericgeens@yahoo.com>, 2021
 # Cas Vissers <casvissers@brahoo.nl>, 2021
 # Pol Van Dingenen <pol.vandingenen@vanroey.be>, 2021
 # Gunther Clauwaert <gclauwae@hotmail.com>, 2021
+# Erwin van der Ploeg <erwin@odooexperts.nl>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -19,7 +19,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:40+0000\n"
-"Last-Translator: Gunther Clauwaert <gclauwae@hotmail.com>, 2021\n"
+"Last-Translator: Erwin van der Ploeg <erwin@odooexperts.nl>, 2021\n"
 "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -859,7 +859,7 @@ msgstr ""
 
 #: ../../content/applications/websites/livechat/overview/get_started.rst:10
 msgid "Set up"
-msgstr ""
+msgstr "Opgericht"
 
 #: ../../content/applications/websites/livechat/overview/get_started.rst:12
 msgid ""
@@ -2808,7 +2808,7 @@ msgstr ""
 
 #: ../../content/applications/websites/website/publish/domain_name.rst:120
 msgid ":doc:`/applications/productivity/discuss/advanced/email_servers`"
-msgstr ""
+msgstr ":doc:`/applications/productivity/discuss/advanced/email_servers`"
 
 #: ../../content/applications/websites/website/publish/multi_website.rst:3
 msgid "Manage Multi Websites"

locale/pt_BR/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: grazziano <gra.negocia@gmail.com>, 2020\n"
 "Language-Team: Portuguese (Brazil) (https://www.transifex.com/odoo/teams/41243/pt_BR/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: pt_BR\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Candidaturas"

locale/ru/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Vasiliy Korobatov <korobatov@gmail.com>, 2019\n"
 "Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: ru\n"
 "Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Приложения"

locale/uk/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
 "Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: uk\n"
 "Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9) || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3);\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "Заявки"

locale/uk/LC_MESSAGES/finance.po

@@ -1389,7 +1389,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:32
 msgid "Manually create a write-off on clicked button"
-msgstr ""
+msgstr "Вручну створити списання через натискання кнопки"
 
 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:34
 msgid ""
@@ -1423,7 +1423,7 @@ msgstr ""
 
 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:57
 msgid "Match existing invoices/bills"
-msgstr ""
+msgstr "Співставити існуючі рахунки клієнтам/постачальників"
 
 #: ../../content/applications/finance/accounting/bank/reconciliation/reconciliation_models.rst:59
 msgid ""

locale/uk/LC_MESSAGES/index.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,6 @@ msgstr ""
 "Language: uk\n"
 "Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9) || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3);\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr ""

locale/zh_CN/LC_MESSAGES/applications.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Mandy Choy <mnc@odoo.com>, 2020\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: zh_CN\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ../../content/applications.rst:3
+#: ../../content/applications.rst:5
 msgid "Applications"
 msgstr "应用"

locale/zh_CN/LC_MESSAGES/index.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 13.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-14 17:10+0200\n"
+"POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2019-10-03 09:46+0000\n"
 "Last-Translator: Mandy Choy <mnc@odoo.com>, 2021\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n"
@@ -21,6 +21,6 @@ msgstr ""
 "Language: zh_CN\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr "Odoo 用戶文档"

locale/zh_CN/LC_MESSAGES/productivity.po

@@ -12,10 +12,10 @@
 # LINYUN TONG <tong.linyun@elico-corp.com>, 2021
 # Datasource International <Hennessy@datasourcegroup.com>, 2021
 # Martin Trigaux, 2021
-# 稀饭~~ <wangwhai@qq.com>, 2021
 # F4NNIU <sparkamax@gmail.com>, 2021
 # Mandy Choy <mnc@odoo.com>, 2021
 # 新 陈 <powersstar@163.com>, 2021
+# 稀饭~~ <wangwhai@qq.com>, 2021
 # 
 #, fuzzy
 msgid ""
@@ -24,7 +24,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-14 16:05+0200\n"
 "PO-Revision-Date: 2021-05-14 16:39+0000\n"
-"Last-Translator: 新 陈 <powersstar@163.com>, 2021\n"
+"Last-Translator: 稀饭~~ <wangwhai@qq.com>, 2021\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/odoo/teams/41243/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -104,6 +104,9 @@ msgid ""
 "device-or-application-to-send-email-using-"
 "Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
 msgstr ""
+"Office 365邮件服务器无法方便地从Odoo这样的主机发送外部邮件。请参阅`微软文档 <https://support.office.com"
+"/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-"
+"email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__，了解如何设置。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:39
 msgid "How to manage outbound messages"
@@ -152,6 +155,8 @@ msgid ""
 " relays are not compatible with Odoo Online unless you configure Odoo to "
 "force the outgoing \"From\" address (see below)."
 msgstr ""
+"如果您在前提下运行 Odoo，您可以使用 Office 365 服务器。Office 365 SMTP 继电器与 Odoo 在线不兼容，除非您配置 "
+"Odoo 以强制外向的\"从\"地址（见下文）。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:66
 msgid ""
@@ -254,13 +259,13 @@ msgstr "请注意，出于安全原因，端口25被阻塞。 尝试使用587、
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:113
 msgid "Choose allowed \"From\" email addresses"
-msgstr ""
+msgstr "选择允许的\"From\"电子邮件地址"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:115
 msgid ""
 "Sometimes, an email's \"From\" (outgoing) address can belong to a different "
 "domain, and that can be a problem."
-msgstr ""
+msgstr "有时，电子邮件的\"From\"（传出）地址可能属于不同的域，这可能是一个问题。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:118
 msgid ""
@@ -270,12 +275,15 @@ msgid ""
 "that kind of usage for security (kudos for that), the Odoo's redistributed "
 "email would get rejected by some recipients' mail servers."
 msgstr ""
+"例如，如果有地址  *mary@customer.example.com* 的客户回复邮件，Odoo "
+"将尝试将同一电子邮件重新分发给线程中的其他订阅者。但是，如果域名*customer.example.com*禁止这种安全使用（kudos），Odoo "
+"的再分发电子邮件将被某些收件人的邮件服务器拒绝。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:124
 msgid ""
 "To avoid those kind of problems, you should make sure all emails use a "
 "\"From\" address from your authorized domain."
-msgstr ""
+msgstr "为了避免此类问题，您应该确保所有电子邮件都使用授权域名中的\"来自\"地址。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:127
 msgid ""
@@ -284,11 +292,13 @@ msgid ""
 " to handle these situations. However, that is more complex and requires more"
 " technical knowledge that is not meant to be covered by this documentation."
 msgstr ""
+"如果您的 MTA 支持 "
+"`SRS（发送者重写计划）<https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme>`_，您可以启用它来处理这些情况。但是，这更为复杂，需要更多的技术知识，而这些知识并非本文档所涵盖的。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:132
 msgid ""
 "Instead, you can also configure Odoo to do something similar by itself:"
-msgstr ""
+msgstr "相反，您也可以配置 Odoo 来自己做类似的事情："
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:134
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:188
@@ -299,11 +309,11 @@ msgstr "在一般设置中设置你的域名。"
 msgid ""
 "In developer mode, go to :menuselection:`Settings --> Technical --> "
 "Parameters --> System Parameters`."
-msgstr ""
+msgstr "在开发人员模式下，转到：菜单选择：'设置 -- -- >技术 -- -- >参数 -- -- >系统参数'。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:142
 msgid "Add one system parameter from these:"
-msgstr ""
+msgstr "从这些添加一个系统参数："
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:144
 msgid ""
@@ -311,6 +321,7 @@ msgid ""
 "use the key ``mail.force.smtp.from`` and set that address as value (such as "
 "``outgoing@mycompany.example.com``)."
 msgstr ""
+"如果您希望*all*您的传出邮件使用相同的\"来自\"地址，请使用键\"mail.force.smtp.从\"，并将该地址设置为值（如``outgoing@mycompany.example.com``）。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:148
 msgid ""
@@ -319,6 +330,8 @@ msgid ""
 "key ``mail.dynamic.smtp.from`` and set as value the email address that "
 "should be used in those cases (such as ``outgoing@mycompany.example.com``)."
 msgstr ""
+"如果您想保留使用相同域名的电子邮件的原始 \"From\" "
+"地址，但要更改该地址用于使用不同域名的电子邮件，请使用键``mail.dynamic.smtp.from``，并设置为这些情况下应使用的电子邮件地址（如``outgoing@mycompany.example.com``）。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:157
 msgid "How to manage inbound messages"
@@ -428,7 +441,7 @@ msgid ""
 "Object aliases can be edited from their  respective configuration view. To "
 "edit catchall and bounce aliases, you first need to activate the "
 ":ref:`developer mode <developer-mode>`."
-msgstr ""
+msgstr "对象别名可以从各自的配置视图进行编辑。要编辑捕获和反弹别名，您首先需要激活：参考：'开发者模式<developer-mode>`."
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:214
 msgid ""
@@ -446,10 +459,12 @@ msgid ""
 ":menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`"
 " and look for *Mail: Fetchmail Service*."
 msgstr ""
+"默认情况下，每 5 分钟在 Odoo 本地获取一次入站消息。您可以在：<developer-mode>`.参考：\"开发人员模式\"中更改此值。转到 "
+"：菜单选择：'设置 - >技术 - >自动化 - >预定操作\"，并查找 *Mail: Fetchmail Service*。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:229
 msgid "Set up different dedicated servers for transactional and mass mails"
-msgstr ""
+msgstr "为事务和群发邮件设置不同的专用服务器"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:231
 msgid ""
@@ -461,13 +476,16 @@ msgid ""
 "Postmark for transactional e-mails, and Amazon SES or Sendgrid for mass "
 "mailings."
 msgstr ""
+"Odoo 的电子邮件服务器能够每天在 Odoo SH 云平台上发送 200 封电子邮件。但是，如果需要，您可以使用单独的邮件传输代理 （MTA） "
+"服务器处理事务性电子邮件和群发邮件。示例：使用 Odoo 自己的邮件服务器处理事务性电子邮件，以及发送电网、亚马逊 SES "
+"或邮件枪进行群发邮件。另一种选择是将邮戳用于交易电子邮件，而亚马逊 SES 或 Sendgrid 则用于群发邮件。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:239
 msgid ""
 "A default outgoing email server is already configured. You should not create"
 " an alternative one unless you want to use a specific external outgoing "
 "email server for technical reasons."
-msgstr ""
+msgstr "默认的传出电子邮件服务器已经配置。除非出于技术原因想要使用特定的外部传出电子邮件服务器，否则您不应创建替代电子邮件服务器。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:242
 msgid ""
@@ -478,6 +496,9 @@ msgid ""
 "the priority of transactional e-mail servers as low as the mass email "
 "servers."
 msgstr ""
+"为此，您应该首先激活：`开发人员模式<developer-mode>`。然后转到：菜单选择：'设置 ->技术 - "
+">外向\"电子邮件服务器。在那里，您必须创建两个电子邮件 MTA "
+"服务器设置。一个用于交易电子邮件，一个用于群发邮件服务器。请务必将事务性电子邮件服务器的优先级标记为低至大规模电子邮件服务器。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:247
 msgid ""
@@ -490,6 +511,10 @@ msgid ""
 "Sendinblue and Mailchimp, as your e-mails would be originated from the "
 "xxxx.odoo.com domain."
 msgstr ""
+"现在，转到：菜单选择：'电子邮件营销 ->设置'，并启用*Dedicated Server*。通过这些设置，Odoo "
+"将服务器用于交易电子邮件的低优先级，而此处选定的服务器用于群发邮件。请注意，在这种情况下，您必须设置域名的发送者策略框架 （SPF） "
+"记录，以包括交易和群发邮件服务器。如果您的服务器与 xxxx.odoo.com 一起存在，可用的选项是森丁蓝和邮件，因为您的电子邮件将来自 "
+"xxxx.odoo.com 域。"
 
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:3
 msgid "Email Templates"

redirects.txt

@@ -32,6 +32,9 @@ contributing/documentation/guidelines.rst contributing/documentation/rst_guideli
 
 administration/odoo_sh/documentation.rst administration/odoo_sh.rst # moved during doc-apocalypse (#945)
 
+developer/webservices/upgrade.rst administration/upgrade/process.rst  # removed incorrect page
+developer/misc/api/upgrade.rst administration/upgrade/process.rst  # removed incorrect page
+
 support/user_doc.rst contributing/documentation/introduction_guide.rst  # removed in forward-port of #544 (b109c3af)
 
 contributing/documentation/introduction_guide.rst contributing/documentation.rst  # flatten hierarchy: introduction_guide --> ../
@@ -225,7 +228,7 @@ applications/marketing/survey/overview/time_random.rst applications/marketing/su
 
 administration/db_management/db_premise.rst administration/maintain/db_premise.rst           # /db_management/* -> /maintain/*
 administration/db_management/hosting_changes.rst administration/maintain/hosting_changes.rst # /db_management/* -> /maintain/*
-administration/db_upgrade.rst administration/maintain/db_upgrade.rst                         # /* -> /maintain/*
+administration/db_upgrade.rst administration/upgrade/process.rst                             # db_upgrade -> /upgrade/process
 administration/enterprise.rst administration/maintain/enterprise.rst                         # /* -> /maintain/*
 administration/update.rst administration/maintain/update.rst                                 # administration/* -> administration/maintain/*
 administration/install.rst administration/install/install.rst                                # /* -> /install/*
@@ -233,28 +236,30 @@ administration/deployment/cdn.rst administration/install/cdn.rst
 administration/deployment/deploy.rst administration/install/deploy.rst                       # /deployment/* -> /install/*
 administration/deployment/email_gateway.rst administration/install/email_gateway.rst         # /deployment/* -> /install/*
 administration/deployment/install.rst administration/install/install.rst                     # /deployment/* -> /install/*
+administration/maintain/db_premise.rst administration/maintain/on_premise.rst                # db_premise -> on_premise
+administration/maintain/db_upgrade.rst administration/upgrade/process.rst                    # maintain/db_upgrade -> upgrade/process
+administration/odoo_sh/advanced/upgrade_your_database.rst administration/upgrade/odoo_sh.rst # odoo_sh/advanced/upgrade_your_database -> upgrade/odoo_sh
 
 developer/webservices/iap.rst                           developer/misc/api/iap.rst
 developer/webservices/odoo.rst                          developer/misc/api/odoo.rst
-developer/webservices/upgrade.rst                       developer/misc/api/upgrade.rst
 developer/webservices/localizations.rst                 developer/misc/i18n/localization.rst
 developer/reference/translations.rst                    developer/misc/i18n/translations.rst
 developer/reference/cmdline.rst                         developer/misc/other/cmdline.rst
 developer/reference/guidelines.rst                      developer/misc/other/guidelines.rst
 developer/reference/iot.rst                             developer/misc/other/iot.rst
-developer/actions.rst                           developer/addons/actions.rst
-developer/data.rst                              developer/addons/data.rst
-developer/http.rst                              developer/addons/http.rst
-developer/mixins.rst                            developer/addons/mixins.rst
-developer/module.rst                            developer/addons/module.rst
-developer/orm.rst                               developer/addons/orm.rst
-developer/reports.rst                           developer/addons/reports.rst
-developer/security.rst                          developer/addons/security.rst
-developer/testing.rst                           developer/addons/testing.rst
-developer/views.rst                             developer/addons/views.rst
-developer/javascript_cheatsheet.rst             developer/javascript/javascript_cheatsheet.rst
-developer/javascript_reference.rst              developer/javascript/javascript_reference.rst
-developer/mobile.rst                            developer/javascript/mobile.rst
-developer/qweb.rst                              developer/javascript/qweb.rst
+developer/reference/actions.rst                           developer/reference/addons/actions.rst
+developer/reference/data.rst                              developer/reference/addons/data.rst
+developer/reference/http.rst                              developer/reference/addons/http.rst
+developer/reference/mixins.rst                            developer/reference/addons/mixins.rst
+developer/reference/module.rst                            developer/reference/addons/module.rst
+developer/reference/orm.rst                               developer/reference/addons/orm.rst
+developer/reference/reports.rst                           developer/reference/addons/reports.rst
+developer/reference/security.rst                          developer/reference/addons/security.rst
+developer/reference/testing.rst                           developer/reference/addons/testing.rst
+developer/reference/views.rst                             developer/reference/addons/views.rst
+developer/reference/javascript_cheatsheet.rst             developer/reference/javascript/javascript_cheatsheet.rst
+developer/reference/javascript_reference.rst              developer/reference/javascript/javascript_reference.rst
+developer/reference/mobile.rst                            developer/reference/javascript/mobile.rst
+developer/reference/qweb.rst                              developer/reference/javascript/qweb.rst
 
 services/support/supported_versions.rst administration/maintain/supported_versions.rst       # services/support/* -> administration/maintain/*

requirements.txt

@@ -1,4 +1,3 @@
-docutils~=0.14
 pygments~=2.6.1
 pygments-csv-lexer~=0.1
 pysass~=0.1.0