An upgrade refers to a change of version (by e.g. from 13.0 to 14.0)

• SH Databases : Create an upgrade request at http://upgrade.odoo.com

• SaaS Databases : Create an upgrade request with Admin account, from page My databases

• You will receive an email if the upgrade succeeded or failed

  1. Fail : create a ticket
     • Go on http://odoo.com/help and choose option "An issue related to my upgrade (test phase)"
     • Add the subscription or a correct database URL
     • 1 issue by ticket
     • Not choosing the right option means additional delay of treatment for your ticket
  2. Success : begin your tests
     • SH: Download the upgraded db, upload it on a staging branch
     • SaaS: Click on the given link
     • Issues? Get back to point i and open a ticket.
     • Be careful, custom code is never automatically upgraded. Get back to point 1 and open a ticket.

In order to shorten the time required by the customer for his upgrade (and to limit therefore the desertion and never-ending upgrades), we're currently testing feedback in 2 phases for customized db.

1. Provide an as ready as possible database to the customer and an Excel sheet of business flows to check.
2. Schedule with the customer a deadline for his first feedback batch.
   • They should commit and allocate around 1 day by key user
3. Once the first feedback batch has been provided, we'll handle the fixes and provide a newly ready to test database.
   • Fixes focused on business and main issues (traceback, wrong behavior, ...)
4. Schedule with the customer a deadline for his second feedback batch.
5. We'll handle the fixes and provide a newly ready to test database.
   • Fixes focused on aesthetic/fine tuning issues (reports, mail template, images, ...)
6. At this stage, the database should be ready to upgrade and a date should be planned with the customer.
7. One week before the upgrade, a last upgraded db is provided for final check and the upgrade stays planned except for real blocking issues that cannot be handled post upgrade.

• The project "Upgrade Projects" will help you know who handles your customer's upgrade. All issues tickets will be automatically set as sub-tasks of the upgrade project.
• Issues for Standard Databases will stay in "Upgrade Issues" project. Issues for Custom Databases will be transferred to "PSBE Custom Upgrade Issues" project.
• More info on the Automated Actions

• Do you handle upgrades for client on their own repository or in Time and Materials ?

  • No. The client has to be hosted by Odoo and pay maintenance fees.

• What about upgrades for sensitive data?

  • If the customer doesn't want to send us his database for the upgrade, we can do upgrades on the customer's server (online). But, be careful, it's billed in Time and Materials and we cannot estimate the time required for the upgrade.

---

• Follow-up with the functional
• Ask for a upgraded database (if not done already)
• Install your modules on an empty database (locally then on Sh)
• Install your modules on the upgraded database (locally then on Sh)
• Write migrations scripts for the data
• Tests

More details on every step on Upgrade Process

• Where should I check for existing devs?
  • In Ps SaaS Customisation project, check all Done tasks with subscription same as client's one.