On 2015-12-23 10:43, Luis Falcon wrote:
> > Tryton has a clean and reliable way to manage upgrade that works
> > since 7 years. I don't see the point to not use it.
> True. Completely agree and it's a great feature.
> 
> That said, I still think that we need a way for a "run once" code for
> Tryton upgrades. Otherwise, as time and new Tryton version goes on,
> we'll end up with very large __register__ methods, and with an
> increased risk of criteria that was not met before at that point in
> time, could be met in the future, generating a big problem, and hard to
> track.

The idea in Tryton is to removed the old migration once the series ended
long time ago. We still did not do the job but I think 1.* series could
be cleaned now.


-- 
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Attachment: pgpO_DXdwGkaM.pgp
Description: PGP signature

Reply via email to