Breakpad/Status Meetings/2015-10-07: Difference between revisions
< Breakpad | Status Meetings
Jump to navigation
Jump to search
| (2 intermediate revisions by 2 users not shown) | |||
| Line 21: | Line 21: | ||
* (peterbe) How much is the 30min deployment delay a problem to you? | * (peterbe) How much is the 30min deployment delay a problem to you? | ||
** Is it worth prioritizing jp's time to optimize it? | ** Is it worth prioritizing jp's time to optimize it? | ||
** | ** [peter] for one, sometimes forgets to check datadog so longer after I started the deployment | ||
** could we get an IRC notification when the deploy is finished in addition to the delay? | |||
== Project Updates == | == Project Updates == | ||
* (peterbe) 2016, the year Socorro becomes a "Data resource" instead of a "Reports resource"? | |||
** more aggressive expiration of data | |||
** less historical reports | |||
** less reports in general | |||
** better APIs; how do we know which APIs stakeholders *really* need? | |||
** more ElasticSearch and less matviews | |||
=== Deployment Triage === | === Deployment Triage === | ||
| Line 34: | Line 39: | ||
== other business == | == other business == | ||
* Mozlando ideas here: http://pad.mocotoolsprod.net/p/tools-and-systems-mozlando-2015 | |||
== Travel, etc == | == Travel, etc == | ||
Latest revision as of 18:28, 7 October 2015
« previous meeting — index – next week » create?
Meeting Info
Breakpad status meetings occur on Wed at 11: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
- (peterbe) How much is the 30min deployment delay a problem to you?
- Is it worth prioritizing jp's time to optimize it?
- [peter] for one, sometimes forgets to check datadog so longer after I started the deployment
- could we get an IRC notification when the deploy is finished in addition to the delay?
Project Updates
- (peterbe) 2016, the year Socorro becomes a "Data resource" instead of a "Reports resource"?
- more aggressive expiration of data
- less historical reports
- less reports in general
- better APIs; how do we know which APIs stakeholders *really* need?
- more ElasticSearch and less matviews
Deployment Triage
PR Triage
other business
- Mozlando ideas here: http://pad.mocotoolsprod.net/p/tools-and-systems-mozlando-2015
Travel, etc
- Adrian now working only 4 days a week (no Adrian on Fridays)