workspaces and configurations

From: Sankar Vidhagriswaran (sv@vortex.crystaliz.com)
Date: Thu, Mar 16 2000

  • Next message: Geoffrey M. Clemm: "Re: workspaces and configurations"

    Date: Thu, 16 Mar 2000 17:48:00 -0500
    From: Sankar Vidhagriswaran <sv@vortex.crystaliz.com>
    Message-Id: <200003162248.RAA25003@vortex.crystaliz.com>
    To: geoffrey.clemm@rational.com, ietf-dav-versioning@w3.org
    Subject: workspaces and configurations	
    
    Geoff,
    
    This is the way our system implements configurations, workspaces (which we call as work packages because they can
    be submitted to other parties for review), baselines, and releases (the last two being very similar except in the
    properties associated with them).
    
    So, implementationally it is possible and it actually makes for a configuration management system that does not
    force people to learn many different concepts. In other words, one can create distributed configuration management
    systems targeted for completely different audiance this way. For the simple document oriented collaboration
    concepts such as baselines need not be explained whereas for software development teams one could choose to 
    expose releases, baselines, builds, etc. All of these can be built from the same two concepts -- configurations and
    composite configurations.
    
    Sankar