On Dec 1, 2005, at 08:59, Denis Ahearn wrote:
> 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?
No, it sounds like Subversion works exactly the same way. You can
create separate release braches for separate versions which are
active at the same time, and if you fix a problem in one version,
it's up to you to merge that change to the other active versions as
needed.
The real question is: why do you have so many active releases at
once? Sounds like you're just making your life difficult.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 4 20:02:55 2005