weekly mobile app release cycles at yammer
DESCRIPTION
Back in November Yammer started shipping our iOS and Android apps every week. Presented at Facebook's London Mobile Forum 2.0TRANSCRIPT
![Page 2: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/2.jpg)
Why weekly releases?
Lots of small projectsLess schedule dependenciesFaster A/B test resultsVelocity!
![Page 3: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/3.jpg)
Why now?
iOS 7 auto updates… but reviews are still reset
![Page 4: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/4.jpg)
Impact on development
master must always be stableNo long-lived feature branchesFeature flagsIncreased automated testing
![Page 5: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/5.jpg)
Internal dogfooding
Successful CI builds deployedUsers prompted every 12 hoursUsers can force upgradeShake to reportSeparate crash queue
![Page 6: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/6.jpg)
Releasing the app
Short lived release branchesQA runs general regressionsProjects do own QAApple approval == cool down periodAndroid beta channel for a week
![Page 7: Weekly mobile app release cycles at Yammer](https://reader033.vdocuments.mx/reader033/viewer/2022052523/5558c598d8b42a995d8b46f0/html5/thumbnails/7.jpg)
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.