As stated on the sentence above, in case of an issue with the **production**
database, we should open a ticket with the label (production) and not
testing an upgrade.
This commits adapt the test to match the label currently present on
odoo.com/help and the URL to pre-select the correct stage as well
closesodoo/documentation#11520
Signed-off-by: Nathan Marotte (nama) <nama@odoo.com>
We often get questions from customers about errors they see running the
upgrade-script, which are caused by restrictions of their environment. Add a
note that mentions the most important requirements to maybe avoid some of these
questions.
closesodoo/documentation#10940
X-original-commit: 2a5e686783
Signed-off-by: Carsten Wolff (cawo) <cawo@odoo.com>
The phrase is confusing and leads customers to contact support to carry out
the upgrade for them.
closesodoo/documentation#9883
X-original-commit: 51323fba44
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit aims to improve the documentation's navigability by
redefining some categories' purposes and titles.
There is a redirection rule for each documentation page moved.
This ensures that users won't have a 404 error message.
task-3217827
closesodoo/documentation#8056
Signed-off-by: Jonathan Castillo (jcs) <jcs@odoo.com>
The Service Level Agreement has to be updated. Any additional line of
code, without using studio, in standard modules is not supposed to be
covered by the upgrade team. It is slightly different than the point
telling "development of custom modules"
closesodoo/documentation#3448
X-original-commit: f469e4ef81
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
The maintenance fees cover the maintenance of the custom code (whoever
did it) and are not specifically dedicated to custom code written by
Odoo development teams
closesodoo/documentation#3420
X-original-commit: 92de7ccb2d
Signed-off-by: Castillo Jonathan (jcs) <jcs@odoo.com>
