1. Mailing Lists
  2. Contributors
  3. Re: The future of OCB

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: The future of OCB

Re: The future of OCB

Avatar

Re: The future of OCB

by
LasLabs, Dave Lasley
- 05/10/2016 04:30:37
I believe that a forward development fork would be a good thing.

An example of something that cannot currently be accomplished is test coverage for JS, which requires editing the Gruntfile.js to add something like Grunt Qunit. Odoo SA does not utilize test coverage tools, therefore I find it unlikely that a patch would be accepted if someone actually spent the time to do this.

On Oct 5, 2016, at 1:08 AM, Holger Brunn <hbrunn@therp.nl> wrote:

We thought up two repos tonight: OCB which is the stable conservative
branch that rarely needs any patches and reviews because it's
odoo_stable+bugfixes, as we know OCB. But then without the crazy amount
of PRs because this branch is only for fixing and we trust in human
intelligence to understand that.
Then we have OCX or OCBleeding or however you want to call the branch,
to merge stuff that's not outright insane. But an interesting testbed
for adaptions, and this we should merge optimistically. As soon as this
is an official branch, it will get runbot and coverage, so this gives us
a playground for interesting stuff to share


-- 
Therp - Maatwerk in open ontwikkeling

Holger Brunn - Ontwerp en implementatie

mail: holger@therp.nl
web: http://therp.nl
phone: +31 (0)20 3093096
<span id="cid:526974AC-529F-43FB-B4AA-A5D750040A93@c.hoisthospitality.com"><signature.asc>

Reference