Breakpad/Status Meetings/2016-07-27: Difference between revisions
< Breakpad | Status Meetings
Jump to navigation
Jump to search
| Line 45: | Line 45: | ||
=== Handling more PII data in crashes === | === Handling more PII data in crashes === | ||
=== Sending stacks for all crashes from the client === | === Sending stacks for all crashes from the client === | ||
* no new updates since last week | |||
=== Replacing FTPscraper === | === Replacing FTPscraper === | ||
* peterbe met with Michael Shal | * peterbe met with Michael Shal | ||
Revision as of 17:08, 27 July 2016
« previous meeting — index – next week » create?
Meeting Info
Breakpad status meetings occur on Wed at 10:00am Pacific Time.
Conference numbers:
Vidyo: Stability 650-903-0800 x92 conf 98200# 800-707-2533 (pin 369) conf 98200#
IRC backchannel: #breakpad
Mountain View: Dancing Baby (3rd floor)
Operations Updates
- Thanks willkg! https://bugzilla.mozilla.org/buglist.cgi?product=Socorro&component=Infra&resolution=---
Project Updates
- What's up Ruby 2.0 on Travis?
- https://github.com/mozilla/socorro/pull/3403
- Travis vs Leeroy?
- Can we move or resolve ALL bugs in Socorro::Middleware?
- https://bugzilla.mozilla.org/buglist.cgi?product=Socorro&component=Middleware&resolution=---&list_id=13135990
- Perhaps do the same with Socorro::Database
- peterbe resolved the last bug in Socorro::Bixie and asked bmo if they can shut down that component
Deployment Triage
PR Triage
Major Projects
Migrating off of persona
Sending public data to parquet for reading from spark/re:dash
Symbols service refactoring (snappy, somewhat tangental to us)
Signature generation across crash reporters
Splitting out collector
Collecting client-side JavaScript errors
Handling more PII data in crashes
Sending stacks for all crashes from the client
- no new updates since last week
Replacing FTPscraper
- peterbe met with Michael Shal
- Notes: https://public.etherpad-mozilla.org/p/socorro-releng-index-201607
- Reduced down to a couple of important questions about whether the TaskCluster Index has all the right stuff
- and if it does, which exact locations and .json files should we pull down.