Mission #3: migrate from SourceGear Vault to Subversion

[David V]

Here is a project which is critical to the success of open Mises.org
development:

We already have both SCM systems set up on mises.org.

SourceGear Vault works very well for Mises.org currently, so we need a
smooth transition which accounts for all currently functionality.
This will require some tricky configuration of subversion to monitor
the production site for updates.

[DustinT]

David,

Have you looked into GIT? I am currently using http://www.github.com
and I am pretty happy with it.

In response to your post...I don't think what needs to be done is
clear. Are you planning to continue to use SourceGear, in addition to
SVN?

[Stephen Gream]

Might I suggest Kenai.com over github? I quite sure we can run git and
SVN on the same project, plus it will give us access to a Wiki, online
chat and the like

[David Veksler]

> Have you looked into GIT?  I am currently using http://www.github.com

and I am pretty happy with it.

The thing is, I am the primary developer and I use Visual Studio extenstively, so this needs to have good integration with that.  When I tried Git I couldn't figure it out at all. I do use github for browsing various open source projects.

>  Are you planning to continue to use SourceGear, in addition to SVN?

No.

---
Regards,
David V.

PGP Key: http://www.rationalmind.net/david/DavidLeoVeksler.txt

[Stephen Gream]

We could maintain a Hudson server which watched an SVN repository and
checked it into a git one and vice versa when there was changes. The
only problem I can see with that though is that, though, is that there
could be conflicts that need resolution. Alternatively, there is a
plugin for VS called "Git Extensions"
http://sourceforge.net/projects/gitextensions/ It also negates the
need for me to work with that god-awful SVN :P

[David Veksler]

What is the advantage of using Git over SVN for this particular project?

 "Git Extensions" looks like a very primitive UI/shell extension for Windows, but there's no mention of VS.

I kinda sorta understand the theoretical advantages of Git, but it's nevertheless very primitive UI-wise.  I do not find it acceptable to type in arcane console commands as part of my workflow. GUI or bust.

---
Regards,
David V.

PGP Key: http://www.rationalmind.net/david/DavidLeoVeksler.txt

[David Veksler]

>  "Git Extensions" looks like a very primitive UI/shell extension for Windows, but there's no mention of VS.

I take that back, I see the VS integration option now.

---
Regards,
David V.

PGP Key: http://www.rationalmind.net/david/DavidLeoVeksler.txt

[Stephen Gream]

"I kinda sorta understand the theoretical advantages of Git, but it's
nevertheless very primitive UI-wise. I do not find it acceptable to
type in arcane console commands as part of my workflow. GUI or bust."

Pfft, Windows developers :P How much do you need for version control
anyway? As far as I can see, it has a minimal, unbloated UI with a
shallow learning curve :)

" "Git Extensions" looks like a very primitive UI/shell extension for
Windows, but there's no mention of VS."

One of the comments says "Great integration with VS", so I kind of
assumed it would have some level of integration

"What is the advantage of using Git over SVN for this particular project?"

-Three words: Local Version Control
It has a dead simple two stage commit, meaning I can commit to my
local branch and test without need to slap the dev server with dodgy
code :)
-It's faster
The speed at which you can perform a merge and switch branches is
faster compared to SVN due to the distributed nature of the client
-Automatic line ending conversion
I'm mostly a Linux guy, so anything I contribute will be done with a
newline char, which windows doesn't do anything with without first
seeing a carriage return (Yes, the age old feud continues >_>)
-Far smaller and leaner client
-Less space is needed for a repository

There's a slightly more balanced comparison here
http://git.or.cz/gitwiki/GitSvnComparsion :)

[Randall Sutton]

David,

Personally I'm fine with whatever as long as it isn't SourceSafe :)

SVN has more visual studio support, but Git and Mercurial make branching easier.  Each has their strengths, so I think whatever works best for you is what we should use.

Thanks,
Randall

[Dustin Townsend]

GitHub is what made me try GIT, b/c I enjoy browsing code in the way they have it. 

I was sold on the fact that it was lean and used the command line... My personal preference is to use the CMI when it makes sense.  I also thought the size of the repos were smaller than the SVN...

I don't think using SVN is a deal breaker... Just I like GIT, so I though I would see if you had considered it.

Also, do you find value in using version control inside VS?  I tried it, but it seemed to slow me down.  I try to keep a min amount of extras installed in VS

Another side note, I use Windows VS for most of my coding (day job), but I also use a mac textmate for mostly Ruby stuff.

  

Dustin Townsend

[David Veksler]

> Also, do you find value in using version control inside VS?  I tried it, but it seemed to slow me down.  I try to keep a min amount of extras installed in VS

Most of my work these days is in XCode and Eclipse, which have SVN integration. Especially in XCode I find it handy to have lists of pending and outdated files as I work.

With SVN, I used to use Tortoise, which was OK, but I missed the above features.  

---
Regards,
David V.

PGP Key: http://www.rationalmind.net/david/DavidLeoVeksler.txt

[David Veksler]

So who wants to take charge of source migration?  I'm willing to try Git if you hand-hold me through the process.

---
Regards,
David V.

PGP Key: http://www.rationalmind.net/david/DavidLeoVeksler.txt

[Stephen Gream]

I've got git-svn, so I'm not too fussed whatever is chosen, I can use
git no matter what :)

[Randall Sutton]

I say we stick with svn because it is the lowest common denominator.  That way if you want to use svn you can and if you want to use git you can use git-svn.