c2c-oerpscenario team mailing list archive

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

Hello Olivier,

let me just suggest to encourage your OPW customers to also report bugs on
Launchpad (aside from reporting via OPW channel): it encourages synergies
(it's quite likely that an OPW bug is actually patched by the community) and
it will show the community that purchasing an OPW contract tend to make a
difference, otherwise it's pretty hard to show the added value to our
customers.

-- 
Raphaël Valyi
Founder and consultant
http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
+55 21 2516 2954
www.akretion.com



On Mon, Aug 29, 2011 at 6:20 AM, Olivier Dony (OpenERP) <
783670@xxxxxxxxxxxxxxxxxx> wrote:

> On 08/28/2011 10:58 AM, Ferdinand @ Camptocamp wrote:
> > I realy would be happy to see OpenERP taking accounting issues more
> > seriously as a service for partners, who will be exposed to customer
> > complaints especially if financial authorities might  doubt that OpenERP
> > accounting provides reliable data.
>
> We are taking accounting issues very seriously, like all others.
>
> In the bug management policy I linked to, you will see that partners or
> customers who need a fast and guaranteed response time should report
> bugs via the OpenERP Enterprise/OPW *service* channel, not Launchpad.
> This is the guaranteed service channel for partners and customers, and
> it's also the right way to request fixing a stable branch.
> The policy has not changed since November 2010.
>
> To be very clear: there is *no guarantee* on response time nor backport
> in stable branches for bugs that are reported on Launchpad (for all the
> reasons explained in the bug management policy - please read it).
>
> Thanks for your understanding
>
> PS: nothing prevents reporting bugs on Launchpad as well, but you should
> not expect any kind of guaranteed service for these unless you report
> them using the proper channel (you could simply mention the LP bug number)
>
> --
> You received this bug notification because you are a member of OpenERP
> Drivers, which is subscribed to OpenERP Addons.
> https://bugs.launchpad.net/bugs/783670
>
> Title:
>  account - level - wrong computation
>
> Status in OpenERP Modules (addons):
>  Fix Committed
>
> Bug description:
>  account/account.py
>
>  def _get_level
>
>  currently the calculated level (except level 1) is very much random,
>  depending on the sequence of processed records
>
>  2 issues:
>  1) IMHO the function makes the wrong assumption that the level of the
> parent account is already calculated, which is not necessarily the case
>  2 ) the level (stored=True) of all childs must be recalculated if the
> level of a parent changes. IMHO this would also solve issue 1).
>  change of structure may be done any time manually.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/783670/+subscriptions
>

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/783670

Title:
  account - level - wrong computation

Status in OpenERP Addons (modules):
  Fix Released

Bug description:
  account/account.py

  def _get_level

  currently the calculated level (except level 1) is very much random,
  depending on the sequence of processed records

  2 issues:
  1) IMHO the function makes the wrong assumption that the level of the parent account is already calculated, which is not necessarily the case
  2) the level (stored=True) of all childs must be recalculated if the level of a parent changes. IMHO this would also solve issue 1).
  change of structure may be done any time manually.

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