CrashKill/StabilityWeek2013/Actions: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 81: | Line 81: | ||
| ? | | ? | ||
|- | |- | ||
| Stats | | Socorro: Stats | ||
| lonnen | | lonnen | ||
| File a bug and do something about it. | | File a bug and do something about it. | ||
| {{bug|908334}} | | {{bug|908334}} | ||
| FIXED | | FIXED | ||
|- | |||
| Socorro: future of dev | |||
| rhelmer | |||
| redo Vagrant-lite | |||
| | |||
| ? | |||
|- | |||
| Socorro: future of dev | |||
| rhelmer | |||
| developer HBase polished and working (tmary {{bug|872810}}, rhelmer to follow up) | |||
| {{bug|907964}} | |||
| ? | |||
|- | |||
| Socorro: future of dev | |||
| lonnen | |||
| build new dev env on the VM dumitru gave us | |||
| | |||
| ? | |||
|- | |||
| Socorro: future of dev | |||
| laura | |||
| nag IT for puppet write access for everybody | |||
| | |||
| ? | |||
|- | |||
| Socorro: future of dev | |||
| lonnen | |||
| follow up on options for try | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| KaiRo | |||
| Finish up bug on listing last 3 days of crashes in about:support | |||
| {{bug|765285}} | |||
| poked, awaiting new patch | |||
|- | |||
| Improving User Support after Crashing | |||
| gps | |||
| expose "disable addon with ID X" API from chrome to "healthreport" | |||
| {{bug|912815}} | |||
| filed | |||
|- | |||
| Improving User Support after Crashing | |||
| Arun | |||
| come back for ideas for design changes in the client ([https://etherpad.mozilla.org/ux-stability-workweek Arun's notes]) | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| bsmedberg | |||
| Support classification | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| brandonsavage | |||
| API to say "tell me what classification for this crash is" [Magic 8 ball API] | |||
| {{bug|915667}} | |||
| filed | |||
|- | |||
| Improving User Support after Crashing | |||
| bsmedberg to follow up | |||
| Reduce the junk in the help menu. | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| bsmedberg | |||
| Redesign email flow | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| bsmedberg | |||
| Support article embedded in crash report ? Need to investigate this further for implemantion | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| laura | |||
| Develop plan for processing 100% of crashes only for their support classification | |||
| | |||
| ? | |||
|- | |||
| Improving User Support after Crashing | |||
| laura | |||
| Develop plan for API for Firefox client to query for crash classification | |||
| | |||
| ? | |||
|- | |- | ||
|} | |} | ||
Revision as of 18:13, 25 September 2013
| Session | Person | Item | Bug | Status |
|---|---|---|---|---|
| Rethinking Socorro Storage | laura | Push on the ops/training/support troubles. Try and get some dedicated attention (a person, for instance) allocated to us. | ? | |
| Rethinking Socorro Storage | lonnen | Backups: costed on Amazon Glacier | ? | |
| Rethinking Socorro Storage | laura | Backups: waiting on bmoss to approve the expense | ? | |
| Rethinking Socorro Storage | erik, rhelmer | Write a failing test against some kind of playground environment to expose Thrift failures. Once that's failing, we can do experiments to figure out what's wrong. | ? | |
| Rethinking Socorro Storage | selena | Research alternative connection methods to Thrift | ? | |
| Rethinking Socorro Storage | rhelmer | Rhelmer will look at CM4 and see what we can get out of that for monitoring, etc | ? | |
| Rethinking Socorro Storage | selena | Go shopping for query tools - Cascading, Hive, Impala, etc - must be open source | ? | |
| Rethinking Socorro Storage | selena | Research alternatives to HBase | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | mbrandt | Get Selenium suite polling for new Socorro commits so the tests get run more promptly and we have less trouble tracking down regressions. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | selena | How about some tests for our stored procs? Write some. They'll call the procs through the middleware layer. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | mbrandt | Stop running tests against dev. | ? | |
| Socorro and FHR: Testing, the master plan or the mutating reality | selena, rhelmer, lonnen | Audit stage's config; make sure it's the same as prod. | ? | |
| Socorro: Stats | lonnen | File a bug and do something about it. | bug 908334 | FIXED |
| Socorro: future of dev | rhelmer | redo Vagrant-lite | ? | |
| Socorro: future of dev | rhelmer | developer HBase polished and working (tmary bug 872810, rhelmer to follow up) | bug 907964 | ? |
| Socorro: future of dev | lonnen | build new dev env on the VM dumitru gave us | ? | |
| Socorro: future of dev | laura | nag IT for puppet write access for everybody | ? | |
| Socorro: future of dev | lonnen | follow up on options for try | ? | |
| Improving User Support after Crashing | KaiRo | Finish up bug on listing last 3 days of crashes in about:support | bug 765285 | poked, awaiting new patch |
| Improving User Support after Crashing | gps | expose "disable addon with ID X" API from chrome to "healthreport" | bug 912815 | filed |
| Improving User Support after Crashing | Arun | come back for ideas for design changes in the client (Arun's notes) | ? | |
| Improving User Support after Crashing | bsmedberg | Support classification | ? | |
| Improving User Support after Crashing | brandonsavage | API to say "tell me what classification for this crash is" [Magic 8 ball API] | bug 915667 | filed |
| Improving User Support after Crashing | bsmedberg to follow up | Reduce the junk in the help menu. | ? | |
| Improving User Support after Crashing | bsmedberg | Redesign email flow | ? | |
| Improving User Support after Crashing | bsmedberg | Support article embedded in crash report ? Need to investigate this further for implemantion | ? | |
| Improving User Support after Crashing | laura | Develop plan for processing 100% of crashes only for their support classification | ? | |
| Improving User Support after Crashing | laura | Develop plan for API for Firefox client to query for crash classification | ? |