FAQ

Can I fix bugs directly in OCB ?

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.

Do I need the Odoo CLA signed to submit a patch to OCB branches ?

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.

Does it contains backports ?

Each version is synchronized with the official repository, thus all official backports are included. Additional OCB patches might have been backported manually, it depends.

Does it contains fixes that are not on same Odoo version, but on higher versions ?

Some official fixes are manually backported by the community, depending on the needs of the contributors.

Does it maintains versions that are no more maintained by Odoo ?

Patches for the former versions can still be accepted. There is currently no frozen branch.

Does OCA's runbot use OCB ?

Why is it sometimes behind Odoo ? does it concern minor updates ?

OCB is synchronized daily with Odoo. At worst there can be 24h of delay.

Why should we use OCB instead of Odoo nightly ?

Because it contains more bug fixes than Odoo nightly. And also because it is maintained for a longer time.

How to use OCB ?

See Odoo documentation about installing from source. Use git clone and update frequently.