> Just a quick answer: I've seen some teams who have tried employing this "one
> branch for each customer" strategy.

That's called Software Product Lines, and it works best (for various
definitions of "best") with...

 - a core of common code
 - satellites of custom code
 - wall to wall unit tests that test each customization
 - the differences extracted to metadata, NOT to git branches
 - anything more than 2 clients need migrates to the core.

Put another way, git is not a replacement for metadata configurations
that turn features on and off.

-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to