Weekly Patch Package, keeping Odoo updated
What is an “Odoo patch”?
Every day Odoo makes small improvements to the Odoo program code. These improvements include:
bug-fixes (solutions to reported errors in logic or functions)
improvements in code security and performance
minor changes that improve the user experience
code adaptations to support changes or enhancements in underlying modules or libraries
A patch is a collection of many small changes grouped into a “patch package” that can be applied to your Odoo instance. We prepare a “patch package” for each active Odoo version every week.
How often should you patch your Odoo instance?
Odoo Patch is a change to code and system operation. The changes improve your system reliability, serviceability and security. We recommend that you patch your Odoo system 6-12 times per year, typically once per month.
Why do we release a patch every week, but recommend to patch only once per month?
Odoo releases fixes and updates every night. We bundle the changes into a weekly Patch Package. The package is available for installation on any Odoo instance that urgently requires an update or fix. Deployment it production is NOT automatic.
Sometimes a particular Odoo version or instance needs to be patched very quickly to solve an immediate problem. The weekly Patch Package provides that flexibility. But deployment is a controlled process that requires the support of a consultant and your approval. So deployment is a planned and controlled process.
That said, Odoo is generally a stable and secure system with very few critical code bugs.
To reduce cost and disruption while ensuring the most up to date code we recommend that patches are applied 6-12 times per year.
How does the ad-hoc patch process work for Customers WITH a valid Maintenance Agreement?
The patch package is added to your staging environment every week. It will be tested and deployed together with the next modification of code change you make. In this case the patch process executed as a part of the mod deployment. No additional work of administration is required and the costs are covered by the agreement.
In cases where we identify the need for a patch that should be deployed separately (because it is urgent or because you have not ongoing code changes a Consultant contact you to plan the deployment. In this case the patch will be managed as a unique Support Ticket. The work is covered by your Maintenance Agreement.
How does the ad-hoc patch process work for Customers WITHOUT a valid Maintenance Agreement?
Based on assessed demand the our technician will install a particular (agreed) “patch package” onto your test or staging instance. The code is automatically checked to identify conflicts or errors arising in your customised code (your modifications and addons).
Conflicts in your code must be resolved prior to deployment. You will be contacted to discuss how to resolve code conflicts and errors. We charge for that support.
Once this process is complete a consultant will contact you to discuss if there is any need to test particular functionality or inform you of any known issues or changes that may affect your user experience. Once you and the consultant agree, we will deploy the patch to your production environment (typically 30 mins).
In most cases this will not disrupt your system. However some patches require restarts so you may notice some impairment in performance during the deployment to your live environment.
If you require support to test a specific feature your Consultant can assist you.
The entire process is administered as a Support Ticket
Can Linserv tell me what the patch does and what issues will arise in my instance?
Each patch contains many small changes in code. The exact effect of those changes depends on your specific configuration and how you use Odoo. We cannot identify every possible outcome for every customer instance and use case.
We do our best to advise you about:
why this patch is needed for your instance
if there is some particular testing we would recommend in your case
share the known issues or outcomes from other patched instances
support you as quickly as possible if some issue should arise as a result of the patch
Will I be billed for support related to the patch?
Odoo provides the codes changes as a part of your license agreement (no additional charge)
We package and test the code changes and create a “weekly patch package” for each active version of Odoo (no additional charge)
If you have an active Maintenance Agreement:
Generally the deployment of patches is included in your agreement
The patch will be added to your staging instance and be tested and deployed together with other mods as agreed
If you do not have any active mods the patch will not be deployed
If we feel the patch should be deployed but you have no ongoing mods we will contact you to support deployment.
However:
If you request additional Consultant support test particular processes you may be charged
If you require Consultant support for a specific deployment time (out of hours) or sequence you may be charged
If you do not have an active Maintenance Agreement you will be charged for consultant support related to:
Preparation and deployment to test (typically 2-4 hours)
Any code fixes or database corrections required for your code or database to allow for the patch (as required)
Consultant support related to testing (as incurred)
Deployment to production environment (typically 30 min)