Managing multiple software releases
I am looking for source control alternatives to Visual SourceSafe, and I'm
specifically interested in ones that can help me manage multiple releases of
my software. With VSS, each time we start a new release of our software, we
perform a "share and branch" on the previous version, which results in an
identical but separate copy of our source tree. While this approach does
allow us to maintain, service and build older versions, while simultaneously
building the latest version, it also results in a lot of extra maintenance
due to having multiple copies of our source code. If you fix a defect in a
previous version, you then have to check each subsequent version to see if
the defect exists there.
Does Subversion handle this "multiple release" issue more gracefully (i.e.
in a way that provides the ability to maintain multiple versions yet without
using distincly separate source code trees)? If so, how?
Received on Thu Dec 1 16:08:25 2005
This is an archived mail posted to the Subversion Users