launchpad development
OopsTools Sprint
- Where: Campinas, SP, Brazil
- When: 20-24 September 2010
Ursula and Diogo got together for a week to discuss improvements for https://edge.launchpad.net/oops-tools/. One of the goals for this sprint was to have Ursula and Diogo hacking together so Ursula can become more comfortable hacking on oops-tools.
Topics discussed
how to get rid of the reports sent to the launchpad@ list, at most have just a single email sent (e.g. https://pastebin.canonical.com/37802/)
- improve the content of the reports
- provide web ui so developers can generate a customized report with oopses only interesting to them
how to fix bug 461269 in a way that new oops attributes can be used to uniquely identify an infestation
- change pageid to become a first class object rather than an oops attribute, so we can make queries and build reports for them.
User Stories
- Deryck wants to see all OOPSes related to the Bugs team, but without the checkwatches noise.
- Danilo wants to see all OOPSes related to Translations in a single report.
- Robert wants to see reports grouped by pageid
- Julian doesn't want to receive any more email
- Francis, Robert and Jono wants to see an overall state of the production instances
- Gary wants the connection between infestations and Launchpad bug report to be very reliable (i.e. once the tool is taught about a false positive, it should do the right thing the next time)
Action items
Bug XXX: change ErrorSummary object to accept sections so it can be built dynamically
Bug XXX: web ui so developers can generate reports customized to what they need (http://ubuntuone.com/p/HvI/)
Bug XXX: page id should become a first class object
Bug XXX: put the exception value normalization code into the database
Bug 461269: new oops attributes, such as pageid, should be used to uniquely identify an infestation
File RT to have lp-production-configs on devpad automatically updated RT #41653
