Having used all I echo Martin's views apart from the following
Hi James,
A more general rule-of-thumb is to use svn when you have good access
to a shared network infrastructure and for some reason (administrative
maybe?) you need to have a centralized repository for sources.
Git / Mercurial works well when you at times need to work offline and
the nature of your project is somewhat de-centralized (kind-of peer to
peer).
I love git and *always* use it for my personal projects but I prefer
svn at work. Also in the beginning git required a little more
brain-power to use than svn so it may appear to be less newbie
friendly than svn. Currently, they are more-or less as easy to use.
I always prefer git to Mercurial since they are both distributed VCS
but git is said to be as lighting fast. This should be because git is
entirely written in C, Mercurial is Python-based so it most probably
suffers from the overhead of an interpreter.
Have never used bazaar so cannot comment on it. You can try them all
and make your pick.
Martin.
On 3/17/13, James Nzomo <kazikubwa@gmail.com> wrote:
> Hello sw-dev oriented skunks!
>
> I've been raking my head about a SW project for various users, each with
> "slightly" different requirements.
> It's a nightmare coming up with 1 solution that fits all, so i decided to
> experiment with a VC system.
>
> What VCS (among the above) would you recommend for a proprietary sw app?
>
>
> _______________________________________________
>
> *In programming, as in everything else, to be in error is to be reborn.** *
> _______________________________________________
> *
>
> *
>
_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke