openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #03652
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
On 10/27/2013 08:19 AM, Fabien Pinckaers wrote:
Ferdinand,
This is not an issue anymore. The new realease policy fixes this. We
don't do anymore cycles like: develop for 9 months, fix during 3
months, then release.
Now, the trunk is stable. Every new feature in trunk goes to minimum 3
code review before being merged in trunk (the developer, its team
leader if any, functional useability expert (apr), then another
developer not involved in the development).
Fabien,
As per slide 28 of
http://www.slideshare.net/openobject/openerp-2012-openerp-strategy, the
same was supposed to be true for the 7.0 release. Much as we love
OpenERP and appreciate that you put a lot of effort into development and
maintenance, we did not experience the 7.0 release as stable (and I am
not talking about the partner model, but simply the usability of the
core modules). Is it really going to be different this time?
Cheers,
Stefan.
Follow ups
References
-
Proposal to improve communication and make more efficient the inclusion of new branches.
From: Nhomar Hernández, 2013-10-22
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Quentin THEURET, 2013-10-23
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-24
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ronald Portier, 2013-10-24
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Olivier Dony, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Lionel Sausin, de la part de l'équipe informatique Numérigraphe, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Mario Arias, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Olivier Dony, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ferdinand, 2013-10-26
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ferdinand, 2013-10-26
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Fabien Pinckaers, 2013-10-27