8000 [IMP] db_management: Update button changes · victorcel/documentation-user@e1d370a · GitHub
[go: up one dir, main page]
Skip to content

Commit e1d370a

Browse files
bouvydbouvyd
committed
[IMP] db_management: Update button changes
The button and modal have slightly changed in our prod, update the screenshot to better reflect the current state and add some text to adapt to the changes.
1 parent 6a4edf7 commit e1d370a

File tree

2 files changed

+19
-5
lines changed

2 files changed

+19
-5
lines changed

‎db_management/db_online.rst

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50,13 +50,19 @@ Several actions are available:
5050
Upgrade
5151
=======
5252

53-
Make sure to be connected to the database you want to upgrade and access to the
53+
Make sure to be connected to the database you want to upgrade and access the
5454
database management page. On the line of the database you want to upgrade, click
5555
on the "Upgrade" button.
5656

5757
.. image:: media/upgrade1.png
5858
:align: center
5959

60+
You have the possibility to choose the target version of the upgrade. By default,
61+
we select the highest available version available for your database; if you were
62+
already in the process of testing a migration, we will automatically select the
63+
version you were already testing (even if we released a more recent version during
64+
your tests).
65+
6066
By clicking on the "Test upgrade" button an upgrade request will be generated.
6167
If our automated system does not encounter any problem, you will receive a
6268
"Test" version of your upgraded database.
@@ -68,14 +74,22 @@ If our automated system does not encounter any problem, you will receive a
6874
test database, our dedicated team will have to work on it. You will be
6975
notified by email and the process will take up to 4 weeks.
7076
71-
You will have the possibility to test it for 1 month. When you will be ready,
72-
and be sure that there are no problem compared to your actual version, you can
73-
click again on the Upgrade button, and confirm by clicking on Upgrade (the button
74-
with the little rocket!) to definitely switch to the upgraded version of Odoo.
77+
You will have the possibility to test it for 1 month. Inspect your data (e.g.
78+
accounting reports, stock valuation, etc.), check that all your usual flows
79+
work correctly (CRM flow, Sales flow, etc.).
80+
81+
Once you are ready and that everything is correct in your test migration, you
82+
can click again on the Upgrade button, and confirm by clicking on Upgrade
83+
(the button with the little rocket!) to switch your production database to
84+
the new version.
7585

7686
.. image:: media/upgrade.png
7787
:align: center
7888

89+
.. warning :: Your database will be taken offline during the upgrade
90+
(usually between 30min up to several hours for big databases),
91+
so make sure to plan your migration during non-business hours.
92+
7993
.. _duplicate_online:
8094

8195
Duplicating a database

‎db_management/media/test_upgrade.png

3.56 KB
Loading

0 commit comments

Comments
 (0)
0