4 ms·
"At Etsy, we are releasing changes to code and application configs over 25 times a day." Perhaps I'm old fashioned, but 25 times a day? I'm very curious as to
by smoody 16y ago
"At Etsy, we are releasing changes to code and application configs over 25 times a day."
Perhaps I'm old fashioned, but 25 times a day? I'm very curious as to the types of changes. UI tweaks? Bug fixes? Do they have to make a config change every time someone creates a new store?
Not judgmental, just curious.
- steveklabnik 16y agoWhen you have a good test suite, and automated deployments, eventually you move into the "deploy on every commit" strategy. For more on this kind of thing, http://timothyfitz.wordpress.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/ http://timothyfitz.wordpress.com/2009/02/10/continuous-deplo... and http://www.startuplessonslearned.com/search/label/continuous%20deployment http://www.startuplessonslearned.com/search/label/continuous...
- mcfunley 16y agoOften 40+ times. 25 is closer to the average, though. UI tweaks, bug fixes, config changes, and quite a lot of work on unreleased features. We never do giant deploys for new user-facing features. When they're released they've been running in production well in advance, and the product release is just a config change.