[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Microsoft Team Foundation vs Subversion

From: John <jsparrow_at_ecclescollege.ac.uk>
Date: 2005-07-28 23:35:18 CEST

Gábor Szabó <szabgab <at> gmail.com> writes:

> People around are talking about postponing their SCM move till the next
> best thing on earth will come in the form of Microsoft Team Foundation.

I like the idea of 'shelving' very much (ie personal save-points).

I've been thinking up a procedure to achieve this on SVN, and came up with:

Branch the trunk;
Commit your save points as and when needed (no one else should use your
branch);
When finished, create a patch file from start of branch to it's end;
Switch to trunk (revision you started on);
Apply your patch;
Commit (or update, merge and commit as needed. Your change appears in trunk
as one changeset, as intended);
Delete your branch;
Done.

When we get 'svnadmin obliterate' you can remove your temp branch from the
repository for good.

The other thing that's interesting in VSTS is formal merge tracking. And it's
SOAP based, not webDAV. That may be a downside I guess (no webfolder
autoversioning), but you do get to design your own protocol (in an XMLly
kinda way). That may improve clarity.

The guys at MS promise it's been designed with offline, remote development
in mind. I'm definatly going to look at it for internal development when
it's released.

But it's very expensive, so for remote development with partners I will stick
to SVN.

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 28 23:38:43 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.