Imagine we have release cycle for every two weeks, but need to build a feature that's going to take three months to complete. How do you use Continuous Integration to keep everyone working on the mainline without revealing a half-implemented feature on your releases?
To solve the issue: We have a configuration file that defines a bunch of toggles for various features you have pending. The running application then uses these toggles in order to decide whether or not to show the new feature. Mode info@ http://martinfowler.com/bliki/FeatureBranch.html http://en.wikipedia.org/wiki/Feature_toggle On 12/10/13 7:10 PM, "Uli Kusterer" <witness.of.teacht...@gmx.net> wrote: >On 10 Dec 2013, at 14:31, Appa Rao Mulpuri <appar...@ivycomptech.com> >wrote: >> Do we have toggle framework in Cocoa? I searched in the internet and >>found http://www.togglz.org/, which is written in Java. I am curious, we >>have equivalent in Cocoa as well. > > >What does it do? > >-- Uli Kusterer >"The Witnesses of TeachText are everywhere..." > > > This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
