Thanks for your feedback. I also see that merging is a weak point of
SubVersion (Many complaints about this feature). But I still consider
about how to define the scale of one project. One project considered as
large project maybe it has:
+ Many developers work on this project
+ Many files are generating and handling in this project
+ Numbers of versions of the product (branching)
+Number of features for this project
Or any other factors can be considered.
Some comments evaluated SubVersion as one potential CM but which levels
SubVersion will work effectively. Actually, I don't have so much
information about how many rather medium and large projects applied
SubVersion and I'd like to need how it works on those projects.
In the other hand, VSS will have one successor which evaluated
impressively: Team System. Can we have any information to compare
capability between SubVersion and Team System :) . And Team System of
Microsoft can cover problems which VSS and even SubVersion faced?
Hope to receive any ideas about this topic.
From: David Weintraub [mailto:email@example.com]
Sent: Friday, July 08, 2005 1:35 PM
To: Nguyen, Tin Chanh
Subject: Re: SubVersion - Pros and cons in big projects
My favorite comment on VSS came from a developer in Microsoft: Your
source would be much safer if you simply printed it out to hard copy
and shredded it than storing it in VSS.
Microsoft uses ClearCase as its Version Control System of choice if
that tells you anything about the trustworthiness VSS.
In any project, I would prefer Subversion over VSS. However,
Subversion is missing some key features that would make it easy to use
for very large corporate projects. The one we recently discussed is
merging. SVN doesn't track merges. In a small project where you can
watch everyone and merges and branching is rare, this isn't a problem.
However, in a large project where you have lots of branches, merging,
and too many people to keep track of, you may have problems.
That being said, Subversion and Apache are very big projects that use
Subversion as their version control system.
If your company has very large corporate projects, I'd look into using
Perforce or ClearCase as VCS.
On 7/8/05, Nguyen, Tin Chanh <firstname.lastname@example.org> wrote:
> Hi all,
> We are on the way to research SubVersion and evaluate its values as
> Configuration Management software. Before it, we used VSS for almost
> projects. Actually, VSS is not good for big projects and that's why we
> consider to SubVersion. We just only apply it on small projects but
> big projects. Actually, we still do not image how many problems we can
> when we apply SubVersion for big projects. Any risks maybe get from
> we discuss deeply about it? We hope to receive any ideas about this
> especially from technical people or who had experienced to work on it
> big projects.
> Thanks and regards,
> This email may contain material that is confidential, privileged
> attorney work product for the sole use of the intended recipient. Any
> review, reliance or distribution by others or forwarding without
> permission is strictly prohibited. If you are not the intended
> please contact the sender and delete all copies.
This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 8 21:55:33 2005