Stuart James Penrose wrote:
Out of curiosity, why you are moving from subversion?
Subversion has served us well, but we are attracted to the extra
freedom the distributed SCMs seem to provide. Specifically, I think
the our attractions are:
1) They seem to make private, experimental branching more practical.
2) I've always considered a 'checkout' to be a branch (after all, it
is a separate line of code to which changes are made independently of
the line from which it was copied - a branch), and therefore I find
their general treatment of working copies as first class branches
appealing.
3) They give the developer more flexibility when disconnected from the
repository - the complete repository history is avail even when you
have no network connection.
Fair enough. Perhaps I just had a bad experience with distributed
version control system used on large code base in the past. Things from
my list that make them hard to deal with at times:
1) tools and ide support is limited (sometimes only command line is
available)
2) you have to clone whole repository in order to bring local copy, and
if you need a branch you have to clone again (there are tricks on
unix/linux to make it fast, but it is not fast on windows)
3) cloning large repositories over network is very slow (though not too
bad with git)
4) you can't see or compare what others are doing in branches (private
repositories are too private for team work)
5) merging is still pain and history look messy after merging
Anyways, I hope that our little integration would help a little to
work with those version control systems.
Also, have you evaluated git?
We've looked into it briefly. Actually, it was Linux Torvald's google
talk that got us moving in this direction. But we've ruled out git
because it isn't really designed to be cross platform and, despite our
love for *nix, we didn't think it best to standardize on a
platform-specific tool when more portable alternatives existed. Also,
git suffers from the same issues mercurial has regarding the inability
to track empty directories (as I understand it, if you create an empty
package, then commit, that package dir is not in the repo and it will
not show up in a checkout/branch).
What is interesting about git is that it has bidirectional svn2git
bridge, so developers can continue to use svn and work with git repository.
BTW, cygwin already include git tools for windows, so it doesn't seem
like there is a cross platform issue with it.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
