NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[IMP] upgrade: remove ticket go-live mention

Browse Source 
The phrase is confusing and leads customers to contact support to carry out
the upgrade for them.

closes odoo/documentation#9880

Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit is contained in:
XPL 2024-06-21 11:23:23 +02:00
parent 89c308cad4
commit 51323fba44
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/administration/upgrade.rst
View File

@ -280,9 +280,7 @@ 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
<https://odoo.com/help>`__.
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.
@ -293,11 +291,11 @@ still successful, especially if it takes a long time to finish. Fully rehearsing
process the day before upgrading the production database is also recommended. process the 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)
- Poor customer experience (e.g., an eCommerce website that does not work correctly) - Poor customer experience (e.g., an eCommerce website that does not work correctly)
The process of upgrading a production database is similar to upgrading a test database with a few The process of upgrading a production database is similar to upgrading a test database with a few
exceptions. exceptions.