gistfile1.txt

Martin Fowler hat es sehr weise Formuliert wie ich finde:

Feature Flags:

http://martinfowler.com/bliki/FeatureToggle.html
http://code.flickr.net/2009/12/02/flipping-out/

Feature Branch:

http://martinfowler.com/bliki/FeatureBranch.html

Flags:

Sehr interessant dabei:

-----
Release toggles are a useful technique and lots of teams use them.
However they should be your last choice when you're dealing with putting
features into production.

Your first choice should be to break the feature down so you can safely
introduce parts of the feature into the product. The advantages of doing
this are the same ones as any strategy based on small, frequent
releases. You reduce the risk of things going wrong and you get valuable
feedback on how users actually use the feature that will improve the
enhancements you make later.
------


Branches:

Er schlägt ein kombiniertes Prinzip vor, interessant ist dabei aber
folgender Teil der uns sicher treffen könnte.

-----
The main thing that makes me nervous about PI is the influence on human
communication. With CI the mainline acts as a communication point. Even
if Professor Plum and Reverend Green never talk, they will discover the
nascent conflict - within a day of it forming. With PI they have to
notice they are working on interacting code. An up-to-date mainline also
makes it easy for someone to be sure they are integrating with everyone,
they don't have to poke around to find out who is doing what - so less
chance of some changes being hidden until a late integration.
-----