Regression on opening a new supplier/customer voucher due to onchange_date()

[Kevin McMenamin]

latest release (for 6.0.2) for supplier voucher is creating a debug error when opening - see attached file

[Kevin McMenamin (kevin-mcmenamin)]

I also had a look in another database with existing voucher entries - when I click on the new button it displays one of the old entries - plus the debug error as well

[Jignesh Rathod(OpenERP) (jir-openerp)]

Hello Kevin McMenamin,

Thank you for reporting However this is unfortunately out of the scope of the current OpenERP release,
so we cannot implement it in version 6.0 Because we already implemented it in trunk
and it will release soon.If you needs this changes in current stable then you can contact us on <email address hidden> but you have a OPW contract with us.In the mean time, we will mark it as "Won't fix" to indicate that no further progress is expected at the moment.

Thank you!

[Graeme Gellatly (gdgellatly)]

If this is a bug then this is clearly a regression as it used to work fine,
but you refuse to fix? Why?

On Wed, Aug 17, 2011 at 5:48 PM, Jignesh Rathod(OpenERP) <
<email address hidden>> wrote:

> Hello Kevin McMenamin,
>
> Thank you for reporting However this is unfortunately out of the scope of
> the current OpenERP release,
> so we cannot implement it in version 6.0 Because we already implemented it
> in trunk
> and it will release soon.If you needs this changes in current stable then
> you can contact us on <email address hidden> but you have a OPW contract with
> us.In the mean time, we will mark it as "Won't fix" to indicate that no
> further progress is expected at the moment.
>
> Thank you!
>
> ** Changed in: openobject-addons
> Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> https://bugs.launchpad.net/bugs/827636
>
> Title:
> Supplier voucher error
>
> Status in OpenERP Modules (addons):
> Won't Fix
>
> Bug description:
> latest release (for 6.0.2) for supplier voucher is creating a debug
> error when opening - see attached file
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/827636/+subscriptions
>

[Graeme Gellatly (gdgellatly)]

The bug is introduced by OPW team in merge 4742 on 3/8/11. So again why do
you not fix? This behaviour is disgusting, not fixing bugs in a supposed LTS
version just because reporter is community, even when introduced by OPW
team.

On Wed, Aug 17, 2011 at 6:48 PM, Graeme Gellatly <email address hidden>wrote:

> If this is a bug then this is clearly a regression as it used to work
> fine, but you refuse to fix? Why?
>
>
> On Wed, Aug 17, 2011 at 5:48 PM, Jignesh Rathod(OpenERP) <
> <email address hidden>> wrote:
>
>> Hello Kevin McMenamin,
>>
>> Thank you for reporting However this is unfortunately out of the scope of
>> the current OpenERP release,
>> so we cannot implement it in version 6.0 Because we already implemented it
>> in trunk
>> and it will release soon.If you needs this changes in current stable then
>> you can contact us on <email address hidden> but you have a OPW contract
>> with us.In the mean time, we will mark it as "Won't fix" to indicate that no
>> further progress is expected at the moment.
>>
>> Thank you!
>>
>> ** Changed in: openobject-addons
>> Status: New => Won't Fix
>>
>> --
>> You received this bug notification because you are subscribed to OpenERP
>> Addons.
>> https://bugs.launchpad.net/bugs/827636
>>
>> Title:
>> Supplier voucher error
>>
>> Status in OpenERP Modules (addons):
>> Won't Fix
>>
>> Bug description:
>> latest release (for 6.0.2) for supplier voucher is creating a debug
>> error when opening - see attached file
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/openobject-addons/+bug/827636/+subscriptions
>>
>
>

[Graeme Gellatly (gdgellatly)]

And btw, the reason the bug isn't present in trunk is you never forward
ported the fix, so the bug that this merge fixes still exists in trunk.

On Wed, Aug 17, 2011 at 11:18 PM, Graeme Gellatly <email address hidden>wrote:

> The bug is introduced by OPW team in merge 4742 on 3/8/11. So again why do
> you not fix? This behaviour is disgusting, not fixing bugs in a supposed LTS
> version just because reporter is community, even when introduced by OPW
> team.
>
>
> On Wed, Aug 17, 2011 at 6:48 PM, Graeme Gellatly <email address hidden>wrote:
>
>> If this is a bug then this is clearly a regression as it used to work
>> fine, but you refuse to fix? Why?
>>
>>
>> On Wed, Aug 17, 2011 at 5:48 PM, Jignesh Rathod(OpenERP) <
>> <email address hidden>> wrote:
>>
>>> Hello Kevin McMenamin,
>>>
>>> Thank you for reporting However this is unfortunately out of the scope of
>>> the current OpenERP release,
>>> so we cannot implement it in version 6.0 Because we already implemented
>>> it in trunk
>>> and it will release soon.If you needs this changes in current stable then
>>> you can contact us on <email address hidden> but you have a OPW contract
>>> with us.In the mean time, we will mark it as "Won't fix" to indicate that no
>>> further progress is expected at the moment.
>>>
>>> Thank you!
>>>
>>> ** Changed in: openobject-addons
>>> Status: New => Won't Fix
>>>
>>> --
>>> You received this bug notification because you are subscribed to OpenERP
>>> Addons.
>>> https://bugs.launchpad.net/bugs/827636
>>>
>>> Title:
>>> Supplier voucher error
>>>
>>> Status in OpenERP Modules (addons):
>>> Won't Fix
>>>
>>> Bug description:
>>> latest release (for 6.0.2) for supplier voucher is creating a debug
>>> error when opening - see attached file
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/openobject-addons/+bug/827636/+subscriptions
>>>
>>
>>
>

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Kevin and Graeme,

Accept the apologies please.

This was undoubtedly a regression and was originally reported for 6.0.2. We missed out that point.

We confirm the error and it has been fixed on stable by revision 4774 <email address hidden>.

Thanks for your participation here.

[Graeme Gellatly (gdgellatly)]

Thanks Jay, sorry for getting fired up, but also it remains that this fix should probably be forward ported to trunk, as it is not there. To be honest I don't even know what the original bug was but the replacement code looked like it was something to do with multicompany selecting the wrong period or something.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Graeme,

We understand your concern and it was surely a regression and supposed to be fixed in 6.0 series.

Fixes from 6.0 are regularly forward-ported to trunk.

Hopefully, we won't have such issues of missing forward-port in trunk now.

Thanks for your time and response.