openerp-expert-framework team mailing list archive

[Olivier Dony <odo@xxxxxxxxxxx>]

On 10/02/2012 05:42 PM, Valentin LAB wrote:
> I guess that some partners (developer ones especially) would be grateful 
> to have insights of such decision earlier. If this is not possible for 
> various reasons, it might be best for us to discover this directly on 
> the mailing list or whatever channel you choose together with an 
> explanation as you gave here rather than on a bazaar log with no 
> explanation.

Yup, it was a hasty/eager commit indeed, and certainly deserved an explanation
(and a proper commit message, etc.).

So let's elaborate on this. In the future, the idea is to try to keep closer
watch on what modules are included in the "official OpenERP modules",
maintained by OpenERP S.A. Given limited resources, it is better to maintain
fewer modules with a higher quality than the opposite.
We've all been bit at some point by half-finished/half-tested "official"
modules, that we assumed were offering reliable features for customers. And
there were still a few of them in OpenERP 6.1. So with 7.0 we will continue the
sanitization effort and try to drop the remaining experimental/very buggy ones
from the list of officially maintained modules.
We won't delete them, but move each of them (including their bzr history) to
their own community-owned branch, under an umbrella project:
   https://launchpad.net/openerp-extra

Each branch in this project would be named <SERIES>-<MODULE>, e.g.
7.0-web_mobile, and would be registered on OpenERP Apps for the corresponding
series.

We should do the same thing for the deprecated extra-addons branch, splitting
it in small branches with just one module (or a couple of related modules), and
no duplicated ones within one series [1].

Then when/if someone feels like maintaining one of these branches, they could
simply step up and ask for it, then move the branch to a new project/team.

We've started to push experimental exports of some official and some extra
addons in the openerp-extra project, so you can see what it looks like already.
Of course the fact that the branches are named 7.0 doesn't mean the modules are
tested and working in 7.0, it just means that this is the place where the 7.0
version of the module is located (ready to be tested/fixed by anyone who cares)[2].
We're only working on the extra-addons authored by OpenERP S.A. for now, but we
could extend the courtesy to all extra-addons afterwards (what to do with each
module to be discussed in a dedicated thread)

For those worrying about dependency management, here is how it could work in a
nutshell:
- OpenERP Apps would automatically manage dependencies and would be more
integrated inside OpenERP 7.0. So you should be able to pull the dependencies
automatically from within OpenERP. Not everything is decided yet, but it should
allow you to install *any* module from OpenERP Apps[2]
- And for developers who need to grab everything easily we could provide a
simple script (à la bzr_set.py) to grab all branches for a given series from
openerp-extra


I'm sure this raises a ton of questions, so we will post more details about
this soon on the list (and discuss the various extra-addons, if there is enough
interest)


Thanks for your patience and for your constructive feedback :-)



[1] We'd like to enforce having a master branch for each module+version that is
registered in OpenERP Apps, with a unique owner (who could change over time of
course)
[2] OpenERP will certainly raise a warning or something when you install a
module that is not official or not tested to work in your series. OpenERP Apps
will hold the relevant metadata for this.