[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handling multiple implementations

From: Alexander Taler
Subject: Re: Handling multiple implementations
Date: Sat, 21 Aug 2004 13:34:05 -0400

>>>>> "nishad" == nishad  <address@hidden> writes:
  nishad> To: <address@hidden>
  nishad> Subject: Handling multiple implementations
  nishad> Date: Mon, 16 Aug 2004 17:12:19 -0400

  nishad> I would like get an expert advice on How to manage multiple
  nishad> implementation of A product (asp pages). One product implementation
  nishad> is based on our base product, but 5% of The total pages may need some
  nishad> customization.  Can somebody suggest how to manage this scenario
  nishad> Using CVS.

  nishad> Is branching for each implementation a good option?  Is there any way
  nishad> that the changes made to One of the files, which is common to all
  nishad> Implementations be transferred to all the Implementations (for
  nishad> eg. bug fixes, etc.)

In my experience, branching for each customer is a bad idea.  It
results in a lot of merging for any bug fix or feature change.
It allows customizations at any place in the code, which people
inevitably take advantage of, causing merging to be much more
difficult.  Ultimately it results in a much greater code
management overhead.

I would suggest implementing customizations either directly in
the code as options, or into the build system.  In CVS you can
store the base system (hopefully the majority of the code) in one
directory, and the customizations (hopefully small) in another
directory, one for each client.  Setting up such a system is a
lot of work initially, but it is worth it in the end.

Hope this helps,

--    Access CVS through a library. 
PGP:  ID: 0x23DC453B  FPR: 42D0 66C2 9FF8 553A 373A  B819 4C34 93BA 23DC 453B
For every great name in history a hundred others might have been substituted.
        -- Elias Canetti.  Crowds and Power.  (trans Carol Stewart)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]