openerp-india team mailing list archive

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

Hello Olivier,

I agree with what you say. However, I would love OpenERP SA listen more
at experimented partners (given that 80% of the new ones have been hired
by sales actions while they would never had jumped in otherwise and will
just be unable to do the work) so we can ensure such structuring changes
DO HAPPEN at new releases. Otherwise we just keep having releases with
new nice looking features on the surface and things broken internally in
ways that cannot be fixed in a backward compatible way, just like here.
And we all know there are more of such issues. Release management is not
about changing the CSS theme, it's all about packaging backward
incompatible changes together. We often have the feeling OpenERP SA
doesn't listen to us enough, and that's why I tell it here.

Given the changes will not be deployed on the regular 6.1 branch because it's  backward incompatibly broken, I advise to just backport the whole thing (while taking the occasion to double check it). Else, what will happen is that in 2 months we will implement HR and run into the exact same issue and we will ask for backporting the rest of the patch, so I don't see any benefit in trying to filter a sub-patch here to get the thing only half working.
Also consider that this is a major deployment that required a huge effort already and customer is unlikely to migrate before one year to stabilize their implementation investment first, and even more unlikely given OpenERP SA never provided any credible release schedule.

As usual, I understand thing are not as simple as resource availability
and upper management policy is involved, but just taking the occasion to
highlight what are the fundamental issues behind such a technical issue.
Thank you for you work.

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

Title:
  [6.1] decimal precision settings for sale, purchase and hr don’t allow
  to comply with the law when using product price units with more than 2
  digits.

Status in OpenERP Addons (modules):
  In Progress

Bug description:
  Please read the full report with appropriate screenshots:
  https://docs.google.com/document/pub?id=1plcP7U1Fbzbtcu_m2JZLyksnBT6UXwwgjXVu874s-d0

  This is reproducible on head 6.1 on the runbot and is a blocking bug
  for one of our customers with an Enterprise contract here in Sao
  Paulo. Therefor, the bug will be also immediately reported to the
  OpenERP SA support channel.

  Notice that Akretion fixed the bug on trunk (v7) as explained in the
  link. We are here asking for a backport on 6.1 so our customer can
  comply with the law requirements on 6.1.

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