News for hackers. Stuff that matters.

A comment on We are moving the Roslyn code to GitHub.

Re:We are moving the Roslyn code to GitHub by farresito on Sunday January 11, 2015 @05:46AM (#8869641)
What were they previously using before the switch to git? Mercurial?
[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by terrajobst on Sunday January 11, 2015 @10:33PM (#8872375)
The teams that still use centralized version control, such as Windows and Office, are either using Team Foundation Version Control (TFVC) or Source Depot (an internal tool that was built using a source code license of Perforce).

The developer division (DevDiv) currently mostly uses TFVC. For the open source projects this doesn't make a lot of sense though, which is why most these are moving to git.

Of course, we're a big company so you'll also find Mercurial and SVN, especially in MSR. I really hope that you don't find SourceSafe anymore though :-)

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by Watabou on Sunday January 11, 2015 @05:51AM (#8869649)
git != Github.

Github just hosts git repositories. You can use git and not host on Github.

They were using git, but hosting the repository on CodePlex.

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by thesimon on Sunday January 11, 2015 @06:05AM (#8869668)
>We are moving our code to GitHub as well as switching to use git internally

But they were using a different tool internally.

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by taspeotis on Sunday January 11, 2015 @06:18AM (#8869687)
Probably TFS, which Microsoft use quite a bit internally [1].

[1] http://blogs.msdn.com/b/visualstudioalm/archive/2013/08/20/t...

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by josteink on Sunday January 11, 2015 @08:08AM (#8869862)
> Probably TFS, which Microsoft use quite a bit internally

But seemingly less and less so, especially in the SDK-teams. Which is definitely interesting.

If Microsoft's own SDK-developers don't want to use Microsoft's own source-control and ALM-system, but rather prefers Github, what signals does that send? I would sayed mixed at best.

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by ethomson on Sunday January 11, 2015 @10:50AM (#8870233)
Well, we use GitHub to host our git repositories for open source and public projects. We use TFS to host our git repositories that are private and closed source.

GitHub does a great job hosting open source projects. TFS doesn't. I don't think this is a mixed message, we're using the right git hosting service for the job.

[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by chii on Sunday January 11, 2015 @09:08AM (#8869996)
it's an open secret that TFS sucks ass. I dont think anything is going to change that attitude - they might as well use something better, and hence the move.
[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by RyJones on Sunday January 11, 2015 @10:39AM (#8870206)
Not much of a secret. There was open revolt when we were forced to switch in MSN.
[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by tracker1 on Monday January 12, 2015 @06:22AM (#8873312)
It isn't all bad, just a bit painful to administrate... that said, iirc quite a few devs at MS started using git for local versioning long before TFS added support for git.
[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by farresito on Sunday January 11, 2015 @07:50AM (#8869837)
They were not using git. It clearly says in the text that they are switching to git internally, as well.
[ Parent | on HN ]
Re:We are moving the Roslyn code to GitHub by Watabou on Sunday January 11, 2015 @05:49PM (#8871648)
Oh, you're right. I saw git files in their repository and assumed they were already using git: https://roslyn.codeplex.com
[ Parent | on HN ]