vtbassmatt

12 ms·

91.
by vtbassmatt 9y ago
Extension to VSTS [1], sorry. We're working with them on making the extension available to the public. It's possible we could open source it as well; I'll poke around. [1] https://www.visualstudio.com/en-us&#x
92.
by vtbassmatt 9y ago
SD was based on a very old Perforce as well.
93.
by vtbassmatt 9y ago
Lots and lots of external customers, and a handful of internal folks. FWIW Windows was never on TFVC (at least not the main development group).
94.
by vtbassmatt 9y ago
Windows developed an extension that lets them do conflict resolution in the web. We have a server-side API that it calls into, but the extension isn't fundamentally different from using BeyondCompare or $YOUR_FAVORTE_MERGETOOL.
95.
by vtbassmatt 9y ago
edit: forgot, no Markdown here Do you mean across all of Microsoft? Different teams have different structures. Speaking only for TFS and VSTS, we have a single repo containing the code for both, a handful of "adjunct" repos contai
96.
by vtbassmatt 9y ago
Different divisions have had different stances on open source code for a long time. Somewhere I still have the t-shirt from our first "Open Source Day" event back in 2008 (and it's not like that was the first time any MS empl
97.
by vtbassmatt 9y ago
No, we'll keep the SD servers around for a while for servicing older products. We also have a "breadcrumbing" system that lets an engineer follow a file's history back from Git to the old system.
98.
by vtbassmatt 9y ago
As the linked article says, modularizing and living in separate repos was the plan of record for a while. But after evaluating the tradeoffs, we decided that Windows needs to optimize for big, rapid refactors at this stage in its developmen
99.
by vtbassmatt 9y ago
The Windows team developed a tool called "GitTrain" that knew how to: - migrate the tip of a branch to Git (yes, the 300GB number is the tips of all the interesting branches, not the history) - keep a Git branch and a SD branch
100.
by vtbassmatt 9y ago
To be somewhat less cynical, VSS and TFVC were not intended to scale to the size of Windows's codebase, thus they weren't used. And instead of inventing our own thing this time around, we went with (and make contributions back to)
101.
by vtbassmatt 9y ago
By design, yes. There are not (yet) implementations on other OSes.
102.
by vtbassmatt 9y ago
This is all correct. Also, we'd notice someone grabbing the whole 300GB whether it's in 40 SD depots or a single Git repo.
103.
by vtbassmatt 9y ago
More or less: - Availability of tools - Familiarity of developers (both current and potential)
104.
by vtbassmatt 9y ago
GVFS helps in both dimensions, working copy and lots of history. For the lots of history case, the win is simply not downloading all the old content. A GVFS clone will contain all of the commits and all of the trees but none of the blobs. T
105.
by vtbassmatt 9y ago
I just got a request today for an API equivalent to `sd files`, which is not something Git is natively great at without a local copy of the repo.
106.
by vtbassmatt 9y ago
True, but the move to Git is part of our larger "1ES" (One Engineering System) effort across the company. The idea is, if you know how to enlist/build/edit/submit in any team, you know how to do the same in any team
107.
by vtbassmatt 9y ago
Taylor is the dev manager for that area so I'm inclined to believe his correction :)
108.
by vtbassmatt 9y ago
Good questions. TFS is a whole suite of services: 2 version control systems (TFVC and Git), work item tracking, build orchestration, package management, and more. VSTS is the roughly-analogous cloud-hosted version. I'd have to dig up t
109.
by vtbassmatt 9y ago
Most of the large Source Depot users have moved to Git or, like Windows, are in the process of moving to Git. Legacy stuff will probably live on in SD for a long time, possibly forever, for maintenance work.
110.
by vtbassmatt 9y ago
Custom JQuery-based framework, transitioning to React.
111.
by vtbassmatt 9y ago
For now, we're not that smart and simply fetch what's opened by the filesystem. With the cache servers in place, it's plenty fast. We do also have an optional prefetch to grab all the contents (at tip) for a folder or set of
112.
by vtbassmatt 9y ago
Really good question. Actually, splitting Windows up was the first approach we investigated. Full details here: https://www.visualstudio.com/learn/gvfs-design-history/ Summary: - Complicates daily life for every e
113.
by vtbassmatt 9y ago
1. Saeed is writing a really nice series of articles starting here: https://www.visualstudio.com/learn/git-at-scale/ In the first one, he lays out how we think about small/medium/large repos. Summary: s
114.
by vtbassmatt 9y ago
A handful of us from the product team are around for a few hours to discuss if you're interested.
115.
by vtbassmatt 9y ago
The old Yellowstone Trail [1] roadbed is still visible in Redmond, WA [2]. [1]: http://yellowstonetrail.org/ [2]: http://www.historylink.org/File/2363
116.
by vtbassmatt 10y ago
Ha, fair point :)
117.
by vtbassmatt 10y ago
Thank you!
118.
by vtbassmatt 10y ago
Not sure why Visual Studio Team Services is in scare quotes -- that's the product's name. And it's not an open source hosting service, which handily explains why Microsoft's open source isn't hosted there. Disclosur
119.
by vtbassmatt 10y ago
Yes, Windows is migrating to Git.
120.
by vtbassmatt 10y ago
We just published more on our blog: https://blogs.msdn.microsoft.com/visualstudioalm/2017/02/03/...

More ›