3. Bugs in releases causing data loss or performance issues.
Awful documentation.
Announcing a release but having no way for users to consume it.
Telling users they’re plain wrong.
How do we fail our users?
9. How we fail our community
Do we recognize (new) contributors?
When a patch is submitted by non-core authors, do we handle them kindly?
When we see a lot of support questions about a particular question, do we fix our
docs?
10.
11. Do we keep our commitments?
Performance testing
Writing tests with Glusto
Fixing static analysis errors
13. Do we keep our commitments?
Performance testing. The repo is now populated with code. There active contributions
from Performance team.
Writing tests with Glusto. We have more tests than the last time. But there has been no
efforts to write new tests with Glusto by the dev team.
Fixing static analysis errors. We used to be in 900s but we’re now in the 800s.