Community mailing list archives

Re: Policy / safety for code updates

Open For Small Business Ltd, Graeme Gellatly
- 11/06/2016 21:12:51
People will have different preferences, mine is to just monitor commits and if I want something update.  Most bug fixes these days are unrelated to functionality I actually use or corner cases I'd run into.  Nothing bad should happen technically, its pretty rare to get a regression, but every so often a misguided functional one gets through.

On Mon, Nov 7, 2016 at 1:17 PM, Jesse Morgan <> wrote:
Hi there,

I have recently started running Odoo 9 Community for my (small at the moment) retail business.
I am also a software developer, and have been increasingly impressed with the platform, framework, API and implementation of Odoo.

I have already begun writing my own small apps to alter functionality.
I plan to make these available once I have stabilized them a bit more and got the hang packaging them up for public consumption.

I have already come across bugs, one which I went to fix myself; but luckily checked the Odoo git repo for Odoo 9 branch first, and found that a fix had already been merged.

It's great seeing how active and open Odoo is.

My question is this: What is the general policy / thoughts on keeping an Odoo community installation up to date with the latest code changes for that version?

Is it generally considered safe to pull the latest merged code changes (for the version you are running, not a version upgrade)

Or is it likely/possible that a code change may introduce issues for an already deployed Odoo installation, due to changes in database structure or some such?

Any suggestions or pointers here would be great!


Post to: