Belgian(?) English word about to pollute the data model forever; PATCH INCLUDED

[Raphaël Valyi - http://www.akretion.com]

Dear OpenERP quality team,

may be you can apply this patch (and TEST a bit) before releasing to avoid having a famous OpenERP data model with English spelling typo. The patch is for revision #2198

the mrp.production 'date_finnished field' might better name 'date_finished'

We used a sed expression to replace all occurrence so I believe it's quite safe (we replaced in pot, po, xml and py files), but may be you would have to deal somewhat to migrate existing production databases.

Hope this helps,

Raphaël Valyi.

[Fabien (Open ERP) (fp-tinyerp)]

sorry, too late...
We apply for v5.1

Raphaël Valyi - http://www.Smile.fr wrote:
> Public bug reported:
>
> Dear OpenERP quality team,
>
> may be you can apply this patch (and TEST a bit) before releasing to
> avoid having a famous OpenERP data model with English spelling typo. The
> patch is for revision #2198
>
> the mrp.production 'date_finnished field' might better name
> 'date_finished'
>
> We used a sed expression to replace all occurrence so I believe it's
> quite safe (we replaced in pot, po, xml and py files), but may be you
> would have to deal somewhat to migrate existing production databases.
>
> Hope this helps,
>
> Raphaël Valyi.
>
> ** Affects: openobject-addons
> Importance: Undecided
> Status: New
>

--
Fabien Pinckaers
CEO Tiny - OpenERP Editor
Chaussée de Namur 40
B-1367 Grand-Rosière
Belgium
Phone: [phone]
Fax: [phone]
Web: http://openerp.com

Great Achievements Start With Tiny Investments
   -- Marty, 2005

[Niels Huylebroeck (red15)]

When the patch is applied in the next release, will updates take care of migrating the data in these fields to the newly named fields ?

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

IMHO,
if Tiny don't communicate explicitly, clearly and loudly about such an
API changes (recent fiscal position API breakage tells you something?)
+ don't provide the required migration scripts, then I think it's
better to do nothing than applying that patch. That's actually why I
tried ti get it included before v5, Because breaking API before v5 was
more acceptable than during the v5.x series IMHO.
If everything is managed cleanly then of course I think that having no
english erros in the data mode is always better.

On Mon, Feb 9, 2009 at 6:55 PM, Red15 <email address hidden> wrote:
> When the patch is applied in the next release, will updates take care of
> migrating the data in these fields to the newly named fields ?
>
> --
> Belgian(?) English word about to pollute the data model forever; PATCH INCLUDED
> https://bugs.launchpad.net/bugs/326160
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in OpenObject Addons Modules: New
>
> Bug description:
> Dear OpenERP quality team,
>
> may be you can apply this patch (and TEST a bit) before releasing to avoid having a famous OpenERP data model with English spelling typo. The patch is for revision #2198
>
> the mrp.production 'date_finnished field' might better name 'date_finished'
>
> We used a sed expression to replace all occurrence so I believe it's quite safe (we replaced in pot, po, xml and py files), but may be you would have to deal somewhat to migrate existing production databases.
>
> Hope this helps,
>
> Raphaël Valyi.
>

[Christophe Simonis (OpenERP) (kangol)]

Le 09-févr.-09 à 18:55, Red15 a écrit :

> When the patch is applied in the next release, will updates take
> care of
> migrating the data in these fields to the newly named fields ?

Of course...

[Fabien (Open ERP) (fp-tinyerp)]

Yes, migration of such issues are guaranteed in maintenance contracts. (editions)

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hey thank you OpenERP you finally fixed it (18 months later..)!