openerp-india team mailing list archive

[Raphaël Valyi - http://www.akretion.com <1151947@xxxxxxxxxxxxxxxxxx>]

My Opinion about schema changes policies: IMHO being allowed to make an
important change or not is all related to the amount of testing and
communication you do around it.

That is: in general you don't kill yourself in manual testing and
communication and only do the automatic testing which doesn't have a
really big effective coverage. That's why usually you should not make
important changes such as schema in a stable release.

That being said, you can still very well do a change and do a ton of
testing and communicate around apologizing for the change and explaining
why changing is better than letting it broken. Just like you would do if
bug is a security fix for instance.

So IMHO, when the software is at this barely mature stage of
development, with that kind of regressions inside, sometimes trying to
always enforce a policy is stupid and instead efforts should be made to
fix the issues.

If OpenERP was as stable and as rigorous as say a Linux Kernel, I would
never defend breaking rules. But what I say is that the apparent
professionalism given to OpenERP is unfortunately mostly only an
apparent surface, so may be it's just better to simply bite the bullet,
admit things aren't as serious as it looks yet and fix things while it's
time.

Meanwhile I wish one day OpenERP become professional and stable. But to
do that, instead of just enforcing apparent policies, roadmaps will need
to be published and discussed with the community, not just publish a
release note once everything has been screwed by some relatively un-
experienced programmer in the dark of a trunk branch may be/may be not
stable in a year.

So let's talk about how to improve things in the future. There is supposed to be a 7.1 version a 8.0 version? What is the time frame? what is the roadmap for each release?  Speaking about policies, will there be a RC  (Release Candidate) this time may be?
Or will you just publish the magic release  one day as a surprise  with may be some bad magic changes inside and then let things broken under the claim you enforce some professional policy?

Sorry for saying it and please to take that personally. I would love to
see things change, but may be it all starts with stopping denial and
biting the bullet and being professional in the whole product
development cycle, not just when it's too late with the no change
policy.

That being said think you for your work and for trying to fix things.

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1151947

Title:
  Link several addresses on individual partners (not companies)

Status in OpenERP Server:
  Confirmed

Bug description:
  Hello,

  Thanks to the Fabien's Q&A on help.openerp.com regarding how to have
  several addresses on partners, I think the situation is clear enough and well
  explained for companies [0].

  However, I still can't find a good way to link several addresses on
  individual customers, not companies, in a B2C context. I posted a
  question and got no response [1].

  Here is a use case, I'll use it in my hypothesis below.

  Mr Foo lives at Bar Street 1.
  He works at Baz Avenue 150 and usually he wants to receive goods at
  work.

  I see 4 hypothesis for that in OpenERP 7:

  1. I create 2 distinct partners:

  * Mr Leo Foo at Bar Street 1
  * Mr Leo Foo at Baz Avenue 150

  They haven't any links between them.

  Problems:

  * From a usability point of view, this would be a mess, especially if I have
    homonyms. I would never be sure what is the main address of Mr Foo and
    would have difficulties to find his good addresses (even if I set Baz
    Avenue 150 as 'delivery' address, I would also the 'delivery'
    addresses of  his homonym Mr Foo in the searches).
  * I would have wrong accounting entries, sometimes on Mr Foo at Bar
    Street, sometimes on Mr Foo at Baz Avenue

  Conclusion:
  It seems to me that this solution is not applicable due to accounting
  issues.

  2. I put the main address of Mr Foo as `is_company`:

  * Mr Leo Foo at Bar Street 1 is the main record, considered as
    `is_company`.
  * Mr Leo Foo at Baz Avenue 150 is a contact of type 'delivery' linked
    to the Mr Foo company record.

  We would not have accounting issues, because this is already handled for
  companies. The searches and usability would be improved over solution 1.

  Problems:

  * Mr Foo is not a company!
  * This would be totally misleading
  * If any existing or future addons use the field `is_company` to apply
    some logic which should only be applied for companies, we would be
    bloody damned with individuals considered as companies

  Conclusion:
  It seems to me that this would be a good solution, but with a renaming
  of the field `is_company` to something more general (and eventually keep
  a field `is_company` to only keep this information). => too late for v7?

  3. This use case is not supported by OpenERP 7 and has to be coded in a
  community addon.

  Problems:

  * We have to be very sure that this problem will be handled
    in only one way. If a part of the community manages it in one way and an
    other part in another way, we'll start to see incompatibility between
    addons (and OpenERP risks issues for migrations too).

  Conclusion:
  It would be very surprising because this use case is very basic for B2C.
  I think that a so 'low level' part of the datamodel should be defined by
  OpenERP to avoid to compromise higher level addons. A change on theses
  base models can have an impact on all the other addons (see
  base_contact).  But let's admit this hypothesis is the good one.

  I'm alright to create a community addon to handle this use case (by the
  way, this is a prerequisite to synchronize openerp with magento). But I
  expect a strong guidance from OpenERP, I need to know how this link
  should be done (add an `is_individual` field like the `is_company`
  field? Just add the `parent_id` field accessible everytime?) to ensure
  that the community addon's solution won't go against the current with
  OpenERP devs.

  4. I just missed the way to do that

  Conclusion:
  The usability on this point should be improved because no one has ever
  answered to my question :-)

  
  What is the solution advocated by OpenERP and why?
  Thanks

  
  Guewen

  
  [0] http://help.openerp.com/question/4341/on-v61-one-partner-could-have-several-addresses-invoicing-delivery-is-this-still-possible-in-v7/
  [1] http://help.openerp.com/question/135/how-do-i-attach-different-addresses-on-a-individual-customer/

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1151947/+subscriptions