Deplayment Management

Maybe not quite the right forum, but:

I am in need of a tool to manage different configurations one application
for varius customers. Most pieces are common, but there are some specific
reports, logos or configuration settings. I am not sure if storing all this
in a VCS is a good idea.

What I want is:
- Checkout customer A, change something, check in
- Same for customer B
- Update common parts for A and B

Thanks for every input!

Bernd


.

Relevant Pages

  • With Respect To an Investment Application
    ... All these modules are resting on a common ... framework, which does routing, workflow, logging etc. ... country to country. ... There are two main domain objects, User and Customer. ...
    (comp.lang.java.programmer)
  • Re: testing by software house: common practice?
    ... >production master CD to the customer without putting it through testing on ... IMHO it is quite common - it was common 20 years ago and sad to say ... >software skills or technical understanding of Windows.)? ...
    (comp.programming)
  • Re: natural sugars & amino acids
    ... Both configurations are found ... >The common sugars are D. This refers to the highest numbered ... >The common amino acids are L. This refers to the C with the amino ... do essential amino acids exist? ...
    (sci.chem)
  • Re: [FreeBSD 5.3-RC2] Processes STILL hanging in unkillable state
    ... > machines have in common - looks like there's a full range from tuned ... > configurations with eyebrowraisers like PREEMPTION to almost-unmodified ...
    (freebsd-current)
  • Re: Deplayment Management
    ... The processes and how-tos are well known. ... Most pieces are common, ... Why - its just a problem of the right configuration ... just split the common part and the customer specific parts in two ...
    (borland.public.delphi.thirdpartytools.general)