[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: VSS migration to...

From: Olivier Dagenais <olivier.dagenais_at_formark.com>
Date: 2007-05-10 15:43:40 CEST

> > I'll even seed the flamewar: look at git, svn and perforce. like
> > gigantic systems that require multiple adminstrators? substitute
> > clearcase for one of the above. don't care about atomic commits and
> > speed of remote diffing? substitute cvs for one of the above.
> i'd be quite happy with SVN, and i think we could build a successful
> process around it. unfortunately it looks like management wants
> process in a box, which is particularly frustrating because then the
> developers have very little say in the process. we (the developers)
> know the current process is broken and would really like to be
> involved in fixing it. but we don't currently have an argument that
> will persuade management...

Many open-source projects use the single-committer software development method: http://www.macadamian.com/index.php?option=com_techarticle&task=view&id=18 We have adapted this sort of methodology at our workplace as well. Subversion supports this methodology/process well. Patches are easy to create, send out and apply. (well, a lot easier than VSS, which we switched from) Expect a slight learning curve to get out of the habit of wanting to "check out" (a.k.a. lock) files before you start working on them.

In other words, SVN supports a decent development process out-of-the-box. HTH,

Olivier Dagenais
Software Engineering / Génie logiciel
Formark - Combine the Best of SharePoint® and Livelink®
Phone: 613-599-5173 ext 238
Make sure you don't miss anything: subscribe to the Formark Newsletter:
Received on Thu May 10 15:41:57 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.