SubVersion - Pros and cons in big projects

["Nguyen, Tin Chanh" <ti...@psv.com.vn>]

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 not
in big projects. Actually, we still do not image how many problems we
can face when we apply SubVersion for big projects. Any risks maybe get
from it?  Can we discuss deeply about it?  We hope to receive any ideas
about this topic, especially from technical people or who had
experienced to work on it with big projects.

 

Thanks and regards,

BaByInIT

 



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.

Re: SubVersion - Pros and cons in big projects

[Werner Punz <we...@gmx.at>]

Nguyen, Tin Chanh 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 not 
> in big projects. Actually, we still do not image how many problems we 
> can face when we apply SubVersion for big projects. Any risks maybe get 
> from it?  Can we discuss deeply about it?  We hope to receive any ideas 
> about this topic, especially from technical people or who had 
> experienced to work on it with big projects.
> 
>  
SVN scales pretty well, the only problem I basically have is not really 
SVN related, but some clients become rather slow once you have myriads 
of files on your HD, this is more a combination of svn producing several 
configuratioin artefacts per file and NTFS which does not scale too well 
with many files in one subdir hierarchy.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SubVersion - Pros and cons in big projects

[David Weintraub <qa...@gmail.com>]

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 <ti...@psv.com.vn> 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 not in
> big projects. Actually, we still do not image how many problems we can face
> when we apply SubVersion for big projects. Any risks maybe get from it?  Can
> we discuss deeply about it?  We hope to receive any ideas about this topic,
> especially from technical people or who had experienced to work on it with
> big projects. 
> 
>   
> 
> Thanks and regards, 
> 
> BaByInIT 
> 
>   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. 


-- 
--
David Weintraub
qazwart@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org