Exactly one year ago  this periodical started to provide regular
insights on production stability. The idea was to shorten the feedback
cycle between deployment of code that leads to fatal errors and the
discovery of those errors. This allows more people to find reports earlier,
which (hopefully) prevents them from sneaking into a growing pile of
576 reports were created between 15 July 2018 and 31 July 2019 (tagged
Wikimedia-prod-error). 425 reports got closed over that same time period.
#### 📉 Outstanding reports
Take a look at the workboard and look for tasks that might need your help.
The workboard lists error reports, grouped by the month in which they were
Breakdown of recent months (past two weeks not included):
- November: 1 report left (unchanged). ⚠️
- December: 3 reports left (unchanged). ⚠️
- January: 1 report left (unchanged).
- February: 2 reports left (unchanged).
- March: 4 reports left (unchanged).
- April: 10 of 14 reports left (unchanged).
- May: 2 reports got fixed! (4 of 10 reports left). ✨
- June: 2 reports got fixed! (9 of 11 reports left). ✨️
- July: 18 new reports from last month remain unsolved.
#### 🎉 Thanks!
Thank you to Aaron Schulz, Ariel Glenn, Brad Jorsch, CScott, Daimona, David
Barratt, David Causse, EBernhardson, Gergő Tisza, James Forrester, Jeena
Huneidi, MarcoAurelio, Roan Kattouw, Stephane Bisson, Tchanders, Tim
Starling, Urbanecm; and everyone else who helped by finding, investigating,
or resolving error reports in Wikimedia production. Thanks!