Rolling releases are stable

bug fixes applied and tested

Odoo uses a rolling release mechanism. Let's review how it's done.

Odoo installers are updated daily based on the latest bugfixes applied to the stable branches.

All commits are fully tested by Odoo's continuous integration (CI) system (runbot.odoo.com) and the nightly builds are only published if the tests pass and if the packages install without error.

Odoo stopped releasing arbitrarily "blessed" minor versions in 2011. The minor versions were unnecessary primarily because:

  1.     Minor versions would not pass more tests than the automatically tested ones

  2.     Changes applied to stable branches respect the stable policy, a long list of strict criterions that makes those               changes safe, low-risk, and high-value only

  3.     Minor versions would unnecessarily delay/complexify the delivery of bugfixes to customers and users

So those nightly builds are "tested and stabilized" snapshots for you.

The unstable development only happen in unstable branches: "saas-X" and "master". You could see the "saas-X" branches as the equivalent of debian testing, and "master" as debian unstable.

You should definitely never use those for production systems.

Now of course when it comes to updating software, the golden rule is: if it's working, don't fix it :-)So unless you have a specific bugfix you'd like to pull, you probably should not be pulling updates every day.

As for critical security fixes, there is no dedicated channel for publishing them, because they often depend on earlier fixes. So when there is a security fix, you really must pull the latest version.

We do announce critical security fixes on public channels, including our community mailing list, twitter, and on GitHub. Odoo Enterprise customers also receive prior notifications of these security alerts via a private mailing list.