[IMP] upgrade: modify support information

task-3473194

closes odoo/documentation#8927

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit is contained in:
XPL 2024-04-22 16:48:07 +02:00
parent 9e312a0bdc
commit 791e784f2f
2 changed files with 23 additions and 32 deletions

View File

@ -2,8 +2,6 @@
Upgrade Upgrade
======= =======
.. _administration/upgrade:
An upgrade is the process of moving your database from an older version to a newer :doc:`supported An upgrade is the process of moving your database from an older version to a newer :doc:`supported
version <supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as version <supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as
each version comes with new and improved features, bug fixes, and security patches. each version comes with new and improved features, bug fixes, and security patches.
@ -45,30 +43,23 @@ An upgrade does not cover:
<upgrade/request-test-database>` while also :doc:`upgrading the source code of your custom <upgrade/request-test-database>` while also :doc:`upgrading the source code of your custom
modules </developer/howtos/upgrade_custom_db>`. modules </developer/howtos/upgrade_custom_db>`.
Upgrading in a nutshell Upgrading in a nutshell
----------------------- -----------------------
#. Request an upgraded test database (see :ref:`obtaining an upgraded test database #. Request an upgraded test database (see :ref:`obtaining an upgraded test database
<upgrade/request-test-database>`). <upgrade/request-test-database>`).
#. If applicable, upgrade the source code of your custom module to be compatible with the new #. If applicable, upgrade the source code of your custom module to be compatible with the new
version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`). version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`).
#. Thoroughly test the upgraded database (see :ref:`testing the new version of the database #. Thoroughly test the upgraded database (see :ref:`testing the new version of the database
<upgrade/test_your_db>`). <upgrade/test_your_db>`).
#. Report any issue encountered during the testing to Odoo by `submitting a ticket for an issue
#. Report any issue encountered during the testing to Odoo via the `support page related to my future upgrade (I am testing an upgrade) <https://odoo.com/help?stage=migration>`_.
<https://odoo.com/help?stage=migration>`__.
#. Once all issues are resolved and you are confident that the upgraded database can be used as #. Once all issues are resolved and you are confident that the upgraded database can be used as
your main database without any issues, plan the upgrade of your production database. your main database without any issues, plan the upgrade of your production database.
#. Request the upgrade for the production database, rendering it unavailable for the time it takes #. Request the upgrade for the production database, rendering it unavailable for the time it takes
to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`). to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`).
#. Report any issue encountered during the upgrade to Odoo by `submitting a ticket for an issue
#. Report any issue encountered during the upgrade to Odoo via the `support page related to my upgrade (production) <https://odoo.com/help?stage=post_upgrade>`_.
<https://odoo.com/help?stage=post_upgrade>`__.
.. _upgrade/request-test-database: .. _upgrade/request-test-database:
@ -254,9 +245,9 @@ working correctly and to get more familiar with the new version.
This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo. This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo.
If you face an issue while testing your upgraded test database, you can request the assistance of If you face an issue while testing your upgraded test database, you can request the assistance of
Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option Odoo by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade)
related to testing the upgrade. In any case, it is essential to report any <https://odoo.com/help?stage=migration>`_. In any case, it is essential to report any problem
problem encountered during the testing to fix it before upgrading your production database. encountered during the testing to fix it before upgrading your production database.
You might encounter significant differences with standard views, features, fields, and models during You might encounter significant differences with standard views, features, fields, and models during
testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced
@ -280,20 +271,21 @@ Upgrading the production database
--------------------------------- ---------------------------------
Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded
database can be used as your main database without any issues, it is time to plan the go-live day. It database can be used as your main database without any issues, it is time to plan the go-live day.
can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page It can be planned in coordination with Odoo's upgrade support analysts by `submitting a ticket for
<https://odoo.com/help>`__. an issue related to my future upgrade (I am testing an upgrade)
<https://odoo.com/help?stage=migration>`_.
Your production database will be unavailable during its upgrade. Therefore, we recommend planning Your production database will be unavailable during its upgrade. Therefore, we recommend planning
the upgrade at a time when the use of the database is minimal. the upgrade at a time when the use of the database is minimal.
As the standard upgrade scripts and your database are constantly evolving, it is also recommended As the standard upgrade scripts and your database are constantly evolving, it is also recommended
to frequently request another upgraded test database to ensure that the upgrade process is to frequently request another upgraded test database to ensure that the upgrade process is still
still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the
process the day before upgrading the production database is also recommended.** day before upgrading the production database is also recommended.**
.. important:: .. important::
- Going into production without first testing may lead to: Going into production without first testing may lead to:
- Users failing to adjust to the changes and new features - Users failing to adjust to the changes and new features
- Business interruptions (e.g., no longer having the possibility to validate an action) - Business interruptions (e.g., no longer having the possibility to validate an action)
@ -358,10 +350,9 @@ exceptions.
a filestore. Therefore, the upgraded database filestore must be merged with the production a filestore. Therefore, the upgraded database filestore must be merged with the production
filestore before deploying the new version. filestore before deploying the new version.
In case of an issue with your production database, you can request the assistance of Odoo via the In case of an issue with your production database, you can request the assistance of Odoo by
`support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to `submitting a ticket for an issue related to my upgrade (production)
the upgrade in production. <https://odoo.com/help?stage=post_upgrade>`_.
.. _upgrade/sla: .. _upgrade/sla:

View File

@ -23,8 +23,8 @@ itself. To install the *Manufacturing* app, navigate to :menuselection:`Apps`, s
down to the :guilabel:`About` section at the bottom of the page. The version number is displayed down to the :guilabel:`About` section at the bottom of the page. The version number is displayed
there. there.
To switch to a newer version of Odoo, see the documentation on :ref:`upgrading a database To switch to a newer version of Odoo, see the documentation on :doc:`upgrading a database
<administration/upgrade>`. <../../../../administration/upgrade>`.
Navigation Navigation
========== ==========