The document discusses how feature toggles can help address "merge hells" that can occur with continuous integration. Feature toggles allow incomplete features to be deployed without being released, avoiding the need to rollback deployments. They enable options like A/B testing, canary releasing, and managing experimental and operations toggles. To manage feature toggles, teams should follow mainline development practices, use feature toggle tools, set expiry dates for toggles, and consider toggles as a first step towards continuous delivery.

1. MERGE HELLS?
By @leenasn at #rootconf
Feature Toggles to the rescue

2. xTEAM

7. Familiar?

8. What went wrong?

9. Continuous Integration
“Continuous integration (CI) is the practice, in software
engineering, of merging all developer working copies to a shared
mainline several times a day.”

10. Mainline Development

11. Incomplete Features?

12. Feature Toggles

14. Configuration Files

15. Available tools
● Rollout
● Togglz
● Qandidate-toggle
● Gutter
Ref: http://featureflags.io/feature-flags/

16. ● Deploy != Release
● Avoid Rollback Hells
Release Toggles

17. ● A/B Testing
● Canary Releasing
Experimental Toggles

18. Ops Toggles
● Designing for failure
● Manage Circuit Breakers

19. The Dark Side

21. $$ Question
How to manage it?

22. Expiry Date

23. Cathedral vs Bazaar model

24. Summary

25. ● Follow Mainline Development
● First step towards Continuous Delivery/Deployment
Continuous Integration

26. Feature Toggles
● Deploy != Release
● Quick Experiments
● Set Expiry date

28. http://martinfowler.com/articles/feature-toggles.html
http://www.multunus.com/blog/2016/03/merge-hells-feature-toggles-rescue/
http://www.multunus.com/blog/2013/06/github-workflow-vs-mainline-
development/
References

29. Leena S N
@leenasn / leena.sn@multunus.com