Holger, thanks. Let's then keep the warn_possible_dataloss method and canalize the interesting logs that it generates.
I think we should work this one out one day but until then, I have a simplistic starting point that will at least allow us to put messages in the database when we are ready for that. https://code.launchpad.net/~therp-nl/openupgrade-server/7.0-API-logging/+merge/175132 Holger, if you can live with this for now, we can go ahead with this proposal, only requiring a change in l.41 of the diff (I think l.35 is fine in an INFO log but I would not bother OpenERP administrators with such messages in the polished upgrade report, by which I am ironically demonstrating the need for levelled logging like you suggest). -- https://code.launchpad.net/~sylvain-legal/openupgrade-server/three-functions-for-addons-migration/+merge/174668 Your team OpenUpgrade Committers is subscribed to branch lp:openupgrade-server. -- Mailing list: https://launchpad.net/~credativ Post to : [email protected] Unsubscribe : https://launchpad.net/~credativ More help : https://help.launchpad.net/ListHelp
