This document discusses feature-driven development and the use of feature toggles. It notes that concurrent development can lead to merge conflicts and bugs, but that feature branches and toggles can help address these issues. Feature toggles allow features to be independently activated and deactivated, and provide fallback options, helping with incremental development and release. The document recommends using short-lived feature branches, metadata to describe features, and administration interfaces to manage feature states.
9. @hendrikEbberswww.guigarage.com
Diff of the first commit
<form >
<input type="button" value=„play“ onclick=„rpc.play()“>
</form>
class PlayService {
!
public void play() {
throw new RuntimeException(„Not implemented!“);
}
!
}
13. @hendrikEbberswww.guigarage.com
Concurrent development = Concurrent problems
button on UI
JPA classes
new media service
bugfix #235
trunk
Ribbon interface
removed (50%)
Ribbon interface
removed (100%)
testcommit
refactored most
entities
14. @hendrikEbberswww.guigarage.com
Concurrent development = Concurrent problems
button on UI
JPA classes
new media service
bugfix #235
trunk
Ribbon interface
removed (50%)
Ribbon interface
removed (100%)
testcommit
refactored most
entities
Application can NEVER be released!
30. @hendrikEbberswww.guigarage.com
Take care of your features
FEATURE_1,
FEATURE_2,
FEATURE_3,
FEATURE_4,
FEATURE_5,
. . .
FEATURE_1462,
FEATURE_11463,
Where is my
feature???
Don’t forget
to clean up!
(once a feature is
live for a defined
period of time)