Contributors mailing list archives


Re: OCA Code sprint: sprint topics

Open for Small Business, Graeme Gellatly
- 11/09/2017 19:06:47


I've been doing quite a lot of port work to master already, although master is in a very broken state right now.  There are some subtle changes, but for the most part its pretty easy.  MANY modules currently require zero change at all.  It would be good to have some guidelines of common issues as a lot of modules will only need these minor changes to work.

ir.values -> binding_model_id (for the most part)
force_save for writable readonly fields.
removal of all report stuff, and -> and subsequent moving of printing logic (sorry I forget exact details, but I need some js help for base_report_to_printer)

In fact those could be preidentified and given a beginners track (If there are any).

What would be really really good, is if we identified the important modules early, and took the opportunity to create an issue on github to do any design work (i.e improvements rather than ports), identify duplicate modules etc.

Something I have suggested both in private and public for a long time, is an optional OCA module which "tracks" which OCA modules are in use, entirely anonymously, in order to know where would be good to focus effort.  If that got some widish agreement then that could be a good module and fits well with an OCA distribution, or independently.

I won't be there, like the majority, it would be good if there was a way to participate remotely. I have about 10 critical OCA modules to migrate, most of which are already working on master.  For some I've opened issues already, but naturally not worth looking at until ready.

On Tue, Sep 12, 2017 at 3:53 AM, Pedro M. Baeza (Tecnativa) <> wrote:
Not exactly.

The agreement was that when in 2 versions the module is not migrated, then it's removed, not only one, as that means that any distraction for migrating this module in one version means to double the commits for removing/adding them. The clear example has been v10, where most modules where migrated directly from v8 to v10.


2017-09-11 17:38 GMT+02:00 Maxime Chambreuil <>:
I think we agreed in a previous discussion (a long time ago) that only modules migrated to v10 should be in the v11 branches.

Ursa Information Systems Maxime Chambreuil
Project Manager / Consultant

Ursa Information Systems
1450 W Guadalupe Road, Suite 132
Gilbert, Arizona, 85233

Office:     1-855-URSA ERP x 710
                1-855-877 2377 x 710
Mobile:   1-602-427-5632

On Mon, Sep 11, 2017 at 10:23 AM, David Beal <> wrote:
Thanks Alexandre for this doc

Before migrate to v11 we could define which modules must be remove from source code in v10 ?


Don't you think ?

Bonne journée

David BEAL - Akretion
Odoo Development / Integration

2017-09-11 13:08 GMT+02:00 Alexandre Fayolle <>:
Hello it's me again,

Right now we have identified a small number of sprint topics for the
code sprint.

* Migration of modules to Odoo 10.0: lots of PR to review / finalize / merge

* starting to migrate modules to Odoo 11.0 : lots of reviews to create

* unification of our CI tools (Travis and Runbot) to share a single code
base: Jairo Llopis, Moisés López, Dave Lasley

* OpenUpgrade for v11

* Weblate platform (Jesús Zapata, Moisés López, Alexandre Fayolle)

* OCA Administrative tooling (Joël Grand-Guillaume): help scripting some
administrative tasks for the OCA (repository creation, invoicing...)

* OCA Distribution (Daniel Reis): bootstrap an OCA Branded Odoo distribution

If you want to propose working on a specific topic and be responsible
for the track, please answer this email, and I will add your track to
the list.

The reference document we will try and keep up to date is at

Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex

Post to:

Post to:

Post to:

Post to: