SocorroRoadmap2010

From MozillaWiki
Revision as of 20:56, 31 March 2010 by Aking (talk | contribs) (Renaming Report section to Trend Report, adding links)
Jump to navigation Jump to search

DRAFT
The content of this page is a work in progress intended for review.

Please help improve the draft!

Ask questions or make suggestions in the discussion
or add your suggestions directly to this page.


Related Quarterly Goals

  • Q2: Migrate crash report generation onto new infrastructure (Webdev/IT/Metrics shared)

Client

  • [client team] Gather more information from crashes bug 528657

Hbase related

  • [metrics team] Metrics q2 goals (for background):
    • Replace NFS in production
    • Have cluster doing background processing of 100% of crash reports
    • Provide replacement for Postgres big table
    • [stretch] Developer API, likely to slide to Q3
  • Get individual crash reports running from Hbase [existing goal]

Search

  • (Requires Hbase) Implement a general purpose full text search. Should be able to search on any data associated with a crash, e.g any part of the stack trace and/or module list, any permutation or combination of field values

Trend Reports

  • Explosive Bugs Analysis
    • Automated detection of explosive bugs
    • First stage is bug 519423
    • PRD is needed here
  • Other cloud based correlation reports:
    • Between one report and other related reports: what are the logical correlatons? (PRD needed)
    • Correlation between any single piece of data and another (e.g. plugins, time, etc
      • Replace current correlations HACK with cloud version bug 554373

Process

Better release process

Testing and QA

  • Add QA to release cycle
  • See Test Plan for UI testing
  • More unit tests, more integration tests
  • Validate data sources against each other (e.g. bug 552539, bug 553144) - also look back at similar fixed bugs for test cases
  • Do we want to use Hudson?

Monitoring

  • Write scripts for app level monitoring for IT to hook up to nagios
  • Implement "business logic" monitors: check things like hourly volume via webapp, db, etc
  • Expand application health [dashboard]
    • Some existing bugs on this. What granularity? What is "normal"?
  • [deinspanjer] Hbase monitoring to be expanded

Staging

  • Staging closer to production/more realistic
  • Perf/load test before deployment
  • Better access to staging for testing
    • Best:
      • database write access
      • ability to run scripts
    • Acceptable:
      • log viewing
      • database browsing
      • view config files
      • view automated test output (Hudson?)
    • Install/write some admin tools to accomplish this (may also be useful in production)