[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Managing branches

From: Evert | Collab <evert_at_collab.nl>
Date: 2006-01-03 22:18:51 CET

Brad Appleton wrote:
> My first question/advice would be, are you sure that using separate
> branches is the way to go in this case?
> My experience has usually been that functional and platform variants
> (e.g., slight variations in functional behavior, or in operating
> environment) are usually best handled in the code-structure than in
> the branching-structure.
> 1) There are design patterns such as Template-Method, Strategy,
> Decorator, Builder, and others for encapsulating variation in behavior.
> 2) here is also the "Business Rules" approach
> 3) and there are other design patterns like Configurator or
> Feature-Manager for treating fine-grained functonality (e.g. services)
> its variants as deployment (installation and/or upgrade) settings in a
> configuration database that the application consults and decides which
> logic or which fine-grained behavior (or variant) is applicable at
> various points in the code
> 4) for Platform/API variations, look at Doug Scmidt's "Wrapper Facade"
> pattern.
> The book "Domain Driven Design" by Eric Evans (see
> www.domaindrivendesign.org) has several good sections and "patterns"
> for this sort of thing.

I have the same problem, the main problem doing it in code is, that I'm
developing php; and I'm distributing the source files, as there is no
such thing as compiled code..

Any suggestions on how to deal with this?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 21:19:12 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.