Breakpad/Status Meetings/2009-Sep-09: Difference between revisions
< Breakpad | Status Meetings
Jump to navigation
Jump to search
m (Created page with '* saving Extensions - status update * saving IP addresses * Materialized Views - status update * Socorro Bug Triage * other stuff') |
Samuelsidler (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
* saving Extensions - status update | * saving Extensions - status update | ||
** not on staging yet; should be there by tomorrow | |||
* saving IP addresses | * saving IP addresses | ||
** preventative measures in case we get bogus reports submitted | |||
** warrants a bit of discussion | |||
** do we really want to keep this data tied to a crash report? | |||
** can we store it for only a specific amount of time before removing it? yes, but not easily | |||
** we might be able to do this above the application layer | |||
** ozten has some details on this (not-zeus, but at that level) | |||
** for now, let's sit on it. if we want to implement this later, will involve more people in the discussion | |||
* Materialized Views - status update | * Materialized Views - status update | ||
** on staging at the moment | |||
** quite a few problems with a view of the reports and count consistency | |||
** griswolf and lars are working on fixing them now | |||
** topcrashers by signature should be the same as a query for the same thing; not currently true on stage, like a bug that will be looked at | |||
** hoping to get problems resolved and pushed to production for '''tomorrow night's push''' | |||
* Socorro Bug Triage | * Socorro Bug Triage | ||
* other stuff | * other stuff | ||
Revision as of 20:14, 9 September 2009
- saving Extensions - status update
- not on staging yet; should be there by tomorrow
- saving IP addresses
- preventative measures in case we get bogus reports submitted
- warrants a bit of discussion
- do we really want to keep this data tied to a crash report?
- can we store it for only a specific amount of time before removing it? yes, but not easily
- we might be able to do this above the application layer
- ozten has some details on this (not-zeus, but at that level)
- for now, let's sit on it. if we want to implement this later, will involve more people in the discussion
- Materialized Views - status update
- on staging at the moment
- quite a few problems with a view of the reports and count consistency
- griswolf and lars are working on fixing them now
- topcrashers by signature should be the same as a query for the same thing; not currently true on stage, like a bug that will be looked at
- hoping to get problems resolved and pushed to production for tomorrow night's push
- Socorro Bug Triage
- other stuff