12

2

Please vote up the source control system that you need us to support in our Super Easy Import Into Kiln Tool™ (or add if missing).

Update: Please try our "Import your existing Subversion/Git/Mercurial repository (or even a plain old directory of files on your local machine) into Kiln" tool by clicking the "Download and run the Kiln Import tool" link on any Empty Repository page.

flag
2 
My vision for how the tool should work, would just be a web interface where you provide a URL. For git/mercurial repos, it would work very straight forward. For SVN you might have to specify layout since while the trunk/branches/tags layout is fairly standard, not everybody follows it. My 2 cents. – Daniel Huckstep Oct 18 2009 at 18:16
1 
I think you're going to be pleasantly surprised by what we've got in store. – Benjamin Pollack Oct 19 2009 at 20:13

11 Answers

20

Subversion    

link|flag
15

I use SourceGear Vault, but I can live without my old history.

link|flag
I use Vault too, but CAN'T live without my old history. – johnfx Jan 19 2010 at 16:01
Dito with the vault history. This information is probably the one reason we have not moved to git or mecurial yet. Full FogBugz integration is almost enough of a feature to push us toward Kiln but it will take many a verbose staff meeting to overcome. – Jerome Mar 17 2010 at 17:56
10

Git / GitHub 

link|flag
9

Code on local machine, no source control

link|flag
8

Team Foundation Server (TFS)

link|flag
6

Perforce

link|flag
I also require perforce support. And not just perforce "import" but perforce integration. We us a lot of perforce features, and it is deeply built into our workflow (as it is for all the perforce sites I know). We need perforce integration the way crucible offers it. – sam jones Oct 19 2009 at 4:14
2 
Thanks for the feedback. As mentioned at kiln.stackexchange.com/questions/140/…, we're likely to get perforce "import" in the hands of customers much earlier than full perforce integration. That's actually true for all non-Mercurial SCMs for Kiln version 1.0. – Ben Kamens Oct 19 2009 at 13:00
How many serious dev shops are going to dump their VCS to use Kiln? – sam jones Oct 19 2009 at 18:40
1 
We're hoping quite a few. It's Fog Creek's position that distributed source control is far superior to the old centralized way of doing things, and Kiln 1.0 is the beginning of our attempt to expose user-friendly DVCS and powerful code reviews to those who are stuck in old (but still massively used) systems. If you're unwilling to switch, that's your choice...but we think trial use of Kiln may change your mind. In later versions of Kiln we may provide lots of the code review functionality for non-Kiln SCMs. – Ben Kamens Oct 19 2009 at 21:15
5

Mercurial / BitBucket

link|flag
5

Visual SourceSafe

link|flag
4

CVS

link|flag
2

Accurev import would be a major incentive for my group.

link|flag
0

Store

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.