GuoChen was discussing/asking about git work flows on one of my blog posts a while back. So this is somewhat a long-story-short reply to his question. I have used a variety of git workflow in the past, including git flow. More recently, because of the complexity of system integration required in my teams product, we have decided to adopt a single git branch development workflow instead. One of the biggest issues associated with a single git branch development workflow is the fact that incomplete features get leaked to customers before they are ready for prime time. In view of that, I have built a feature switch for iOS, using a dynamic, backend-generated plist to control availability of features to the end user/customer. The plist is generated on-the-fly, and is consumed by the iOS app frontend (or Android app or Frontend Web app - whatever) in order to decide whether or not to block out specific ViewControllers in the frontend. My implementation is similar to this open source library - https://github/mattt/GroundControl - but has advanced features like roles. Will publish more about our experience with this single branch-feature switch approach for shipping software in due course. Cheers.
Posted on: Thu, 03 Jul 2014 11:13:35 +0000
Trending Topics
Recently Viewed Topics
© 2015