News for hackers. Stuff that matters.
Re:Tracking Every Release by smoody on Wednesday December 08, 2010 @07:42PM (#1985435)
"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.

Re:Tracking Every Release by steveklabnik on Wednesday December 08, 2010 @07:47PM (#1985449)
When 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-deplo... and http://www.startuplessonslearned.com/search/label/continuous...

Re:Tracking Every Release by mcfunley on Wednesday December 08, 2010 @07:54PM (#1985482)
Often 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.