openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #03670
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
>> to put this discussion in perspective, let me give an overview of
>> which schema changes have been put through in ocb-addons/7.0 so far:
>>
>> - An 'active' field was added to account.journal
>> - A sequence field was added to account.tax
>> - A link was created from crm.phonecall.report to crm.lead
> Just to understand the current policy: Are these changes already
> included in trunk?
No.
And they will probably not be merged. (for sure, not in v7 - and
probably not in trunk too)
I may be wrong as I checked very quickly, but:
- active field on account.journal: IMHO it's a serious bug introduced
in ocb branch; if you desactivate a journal containing journal items
you create inconsistencies in all your legal reports. --> We will
not merge this as it's against the rule defined for financial
integrity. (the user should never be able to create inconsistencies)
- adding sequence on account.tax.code.template: as both
account.tax.code and account.tax.code.template have _order="code"
and not _order="sequence" (on both trunk and ocb), I don't think we
should add sequence on account.tax.code.template. --> We should
better remove sequence on account.tax.code as it's not used.
- link from crm.phonecall.report to crm.lead: looks like a very
specific need, so it may be better to put this in a community
module. (otherwise we can add a lot of fields on every report)
> If they are, ok I've been warned it's a backport! If it breaks my
> modules I'll take the blame, and I'm confident there will be no problem
> during automated migration.
>
> If they're not, for me it means I have to eveluate each of them against
> my own modules/patches
> When migrating to later versions I'll have to re-evaluate each of them -
> I do it for my own patches already, I'd rather not do it anymore if/when
> I switch to OCB branches.
--
Fabien Pinckaers
CEO OpenERP
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: +32.81.81.37.00
Fax: +32.81.73.35.01
Web: http://openerp.com
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: Olivier Dony, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Ronald Portier, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Raphael Valyi, 2013-10-25
-
Re: Proposal to improve communication and make more efficient the inclusion of new branches.
From: Stefan, 2013-10-26
-
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-28