c2c-oerpscenario team mailing list archive

["Anup \(OpenERP\)" <ach@xxxxxxxxxxx>]

Hello,

     Our R&D Teams are focused on the latest OpenERP version, and this
issue does not affect it. Our policy is to keep the changes applied on
stable branches to a minimum, in order to limit the regression risks for
customers that are in production. This means that bugs reported on
Launchpad are fixed in the trunk branch only by default, even if they
were reported against other stable versions.

     We stand of course ready to backport the change to stable releases
if it has an impact on any customer. In this case please report it to
our maintenance team via the OpenERP Publisher's Warranty. They will
quickly help solve the issue and backport the fix if needed.

Thank you for your understanding!

** Changed in: openobject-server/5.0
   Importance: Wishlist => Undecided

** Changed in: openobject-server/5.0
       Status: In Progress => Won't Fix

** Changed in: openobject-server/5.0
    Milestone: 5.0.15 => None

-- 
failing crons must report properly
https://bugs.launchpad.net/bugs/433395
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: In Progress
Status in OpenObject Server 5.0 series: Won't Fix
Status in OpenObject Server trunk series: In Progress

Bug description:
currently crons fail quietly 
IMHO there should be a default notification function (sending a requst or mail to the job owner od a dedicated user) which runs if the cron job fails.

I see a problem sending requests to the administrator, because this account will not be used regulary