Commits

Herbert Breunung committed 3d98e6a

rewrote intro feature

Comments (0)

Files changed (1)

doc/CompleteProgramming.pod

 
 =head4 Introducing a feature
 
+When a use case prototype is completed in all details and cleaned up,
+the architect has to decide in when and in which form it will be introduced,
+to prevent experience rot (L<http://www.uie.com/articles/experience_rot/>).
+It will happen during one sprint and via a feature branch that will introduce
+all changes in program, libs, docs and tests as one commit. So even if the history
+of the branch will be preserved - the merge happens with a rebase. As a first
+step the libs with theirs tests will be expanded. After that the caller follow.
 
-
-Only completed features with their tests are acceptable to the main dev branch.
-You may preserve their history in the feature branch, that picked up the code
-from a use case prototype and brought it to insertable form.
-as
-one rebased commit. Preserve history only in the branch if preferred - not in master.
-http://www.uie.com/articles/experience_rot/
-
-This means: at this point we use short lived feature branches,
-that pick the the code from a use case prototype and bring it into the program.
-Try to bring the programm with the merge into a state, where it could be shipped today.
-This not only means that the code is documented, commented and has test coverage.
-Also configs and other auxiliary data like icons should be included.
-If there is an config dialog or config files -  all switches for the new function
-are there and do work. make sure you only rely on included libs or modules that
-are listed in the installer. Please mention also in the comments which prototypes
+If there is an config dialog or config files - all switches for the new function
+are there and do work. Make sure you only rely on included libs or modules that
+are listed in the installer. Please mention also in the comments, which prototypes
 were the basis of this feature.
 
 =head4 Libraries
 
 
+
+
 =head3 Tests
 
 The rise of Extreme Programming (XP) gave also rise to Test Driven Development (TDD),
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.