date:20140319

[Openerp-connector-community] Dev branches for next releases

2014-03-19 Thread Guewen Baconnier


Hi there,

I started to create branches that will be the next releases of the 
connector framework and Magento connector.  They are not freezed; I will 
continue to merge the accepted proposal, but the most adventurous of you 
can already start to use them for development / testing.


The branches:
https://code.launchpad.net/~openerp-connector-core-editors/openerp-connector/7.0-next-release
https://code.launchpad.net/~openerp-connector-core-editors/openerp-connector-ecommerce/7.0-next-release
https://code.launchpad.net/~openerp-connector-core-editors/openerp-connector-magento/7.0-next-release

When upgrading, in addition to the usual update of `connector`, you will 
need to install the module `connector_base_product` that is now a 
dependency of connector_ecommerce (and OpenERP fails won't install a new 
dependency).


Thanks to the contributors!

--
Guewen Baconnier
Business Solutions Software Developer

Camptocamp SA
PSE A, CH-1015 Lausanne
Phone: +41 21 619 10 39
Office: +41 21 619 10 10
http://www.camptocamp.com/

--
Mailing list: https://launchpad.net/~openerp-connector-community
Post to : openerp-connector-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-connector-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] OCB branches, communitiy addons and tests

2014-03-19 Thread Leonardo Pistone

Thanks for raising that important point Nicolas.

Let us check what happened:

https://bugs.launchpad.net/openobject-addons/+bug/924200

If I understand correctly, Raphael Collet is saying that all periods in
demo data are allowed to overlap to allow people to create a chart of
accounts in a demo database. That is a special and non-standard situation
that breaks tests that use periods.

Integration tests (both unittest and yaml) use demo data. That means that
we use a very different setup for production and testing. That is
unfortunate, especially as we gradually start to take testing seriously -
at least there is a good trend in that respect in the community.

Best,
Leo


On Wed, Mar 19, 2014 at 8:41 AM, Nicolas Bessi nicolas.be...@camptocamp.com
 wrote:

 Hello,

 Due this bug
 https://bugs.launchpad.net/account-financial-report/+bug/1281579 we have
 some communitiy addons and MP that have green tests on OCB and red tests on
 official addons.
 That raises an interesting question, should community addons tests in
 priority been green against OCB branch, or official branches ?

  The answer to that question will have an impact on MP review and should
 be written on community review guideline.

 Regards

 Nicolas

 ___
 Mailing list: https://launchpad.net/~openerp-community
 Post to : openerp-community@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openerp-community
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp

Re: [Openerp-community] OCB branches, communitiy addons and tests

2014-03-19 Thread Alexandre Fayolle

On mer. 19 mars 2014 08:41:49 CET, Nicolas Bessi wrote:
Hello,

Due this bug
https://bugs.launchpad.net/account-financial-report/+bug/1281579 we
have some communitiy addons and MP that have green tests on OCB and
red tests on official addons.
That raises an interesting question, should community addons tests in
priority been green against OCB branch, or official branches ?

My vision on this:

1. In the general case, developers should strive to get the tests green
on both branches (OCA and Official). People who have never heard of OCA
and OCB are using community modules downloaded from apps.openerp.com
and having them break when they use the official branches is not a good
experience you are giving them. The end user is certainly not aware of
this issue and he will face the crash. Options : work around the known
bug in the official addon (e.g. by monkey patching until the merge is
done...)

2. in the specific case mentionned above, another similar MP was
rejected by Raphael Collet
(https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-bug-924200-mdi/+merge/91058),
so I'm not sure merging the fix in the ocb addons branch was a good
idea, because it introduces a difference between both branches in the
demo data, and now we have red tests on the official branch, which will
make it hard to find when bugs are introduced in
account-financial-reports. I fear that the MP on the official branch
will never be considered or will be rejected and we will be stuck with
an awkward situation.

I'm interested to know it OpenERP SA's position has evolved since
Raphael's rejection of the MP.

--
Alexandre Fayolle
Chef de Projet
Tel : + 33 (0)4 79 26 57 94

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
http://www.camptocamp.com

___
Mailing list: https://launchpad.net/~openerp-community
Post to : openerp-community@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openerp-community
More help : https://help.launchpad.net/ListHelp

38 matches

Mail list logo