Flickr I've read about DevOps a wikipedia and one aspect of it is not clear for me. How in Flickr they use Subversion? At this presentation: http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr page: 38 - Always ship trunk page: 40 - Example of "branching in code" And there is Trunk for development, release branch to support etc. But how it looks like in Flickr? There is at page 38 "Always ship trunk" so developers must work on branches most of the time? Or first commit is with 'branching if's" in code? Personally I doesn't like a if's for branching idea... Chrome Recently I read about similar approach in Google Chrome Release Cycle in which workflow are embedded configuration options to do branching in code. 1: Everyone works on trunk, then they create stable branch and work on dev and to stabilize branch and ship all scheduled functions. 2: They work on trunk, has 3 channels, trunk, beta a...