3 ms·

Not a bad reaction. With all the reverts is there a QA issue? Or too many releases?

• marcog1 10y ago
  When you do daily deployments, you can't QA every one much. You rely on automated tests and Internal users using the new code for a couple hours before the deployment. We were unlucky in this case with the number of bad releases. Each was relatively minor, and ironically one was to fix a bug with the code that caused this outage. We run a 5 whys for most of them.
  • Mtinie 10y ago
    > When you do daily deployments, you can't QA every one much. In that case, should you be doing daily deployments to production?
    • deleted 10y ago
      [deleted]
  • mathattack 10y ago
    I include automated testing in my definition of QA. (Necessary but not sufficient) Are the daily drops predominately bug fixes or also a regular drip of new functionality? I think the old world of quarterly releases was also bad for other reasons. I'm curious about the right middle point. Every time a company like Asana comes clean about outages and software quality issues, the canon of knowledge improves. Thank you for sharing!