On Wed, Mar 23, 2011 at 5:48 PM, Robert Collins <[email protected]> wrote: > I'm wondering if we should treat javascript errors as critical in the > zero-oops-policy. if we had automated error reporting from javascript > clients, we would trivially treat them as oopses and thus critical. > > We don't have such tooling today, but perhaps we should treat them > with the same severity? >
I'm +1 on treating js errors as critical bugs. They are, IMHO, generally easy to fix too, so yay for easy, critical bugs to fix! We should also require test coverage when fixing these. Also, presumably we mean js errors as reported by Firebug or Chromium's developer console. Maybe we also mean IE errors, but I think it's worth being specific here. As for tooling for automated reporting, I think it's a great idea. Someone should go and do that. ;) /me looks around the room... "Beuller.... Beuller...." FWIW, Paul and I chat daily about js and the dev story across Launchpad and U1, so if U1 gets what Martin shows working, we can look at bringing it over to LP. Cheers, deryck -- Deryck Hodge https://launchpad.net/~deryck http://www.devurandom.org/ _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
