-
-
Notifications
You must be signed in to change notification settings - Fork 402
Because it contains more bug fixes than Odoo nightly. And also because it is maintained for a longer time.
Some official fixes are manually backported by the community, depending on the needs of the contributors.
Patches for the former versions can still be accepted. There is currently no frozen branch.
Each version is synchronized with the official repository, thus all official backports are included. Additional OCB patches might have been backported manually, it depends.
OCB is synchronized daily with Odoo. At worst there can be 24h of delay.
You should install OCB from source with git clone
and update frequently.
- You don't need to clone the whole Git tree, only the branch for your Odoo version:
git clone --single-branch --branch [your Odoo version] [url]
- Add a cron job to regularly update your OCB repository (typically with
git pull [options]
)
See Odoo documentation about installing from source.
OCB only accept changes if you submit your fix against the official version to prevent to be a fork in the end. All updates must be submitted to the official odoo branch for adoption in the official odoo release before they can be considered for the OCB version.
No. But as you need to submit your patch upstream, Odoo SA will probably ask you to sign it. The OCA encourages you to carefully read this document, as it allows Odoo s.a. to relicense your contribution. Some important contributors from the OCA have signed that document because this eases the work of the core maintainers and the OCB maintainers.
The old runbot is using OCB to run, but runboat is not running on Odoo at all.
Website | Online Demo | Community | Documentation | Help