<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>I should just stay out of this....<BR>
<BR>
> widely adoptable on many platforms<BR>
<BR>
"As someone who uses Win32.." There appear to be a few other contenders. Monotone mostly. Maybe git.<BR>
SVN certainly seems to be the all around popularity leader.<BR>
Perforce is excellent and I think free (beer) in this context.<BR>
Gaining in popularity, but not open source.<BR>
<BR>
<BR>
I can't claim to know half of what Olaf knows, but I did do a fair amount of research, with unusual goals.<BR>
I wanted source control just for myself.<BR>
I don't need branching.<BR>
I want changesets. cvs fails.<BR>
I don't want to host anything myself.<BR>
None of my machines are always on. They are all laptops.<BR>
I want to access the content from friend's place.<BR>
I was willing to spend money (and am spending some).<BR>
A Windows-only solution would have been ok, though perhaps not preferred.<BR>
I'd like to be able to see diffs in my current workspace without going to the network.<BR>
Ability to see history without the network is nice but not crucial.<BR>
<BR>
<BR>
The only hosting I could find was for CVS and SVN. This was critical.<BR>
"Code Co-Op" is a Windows-only system that is cheap, "distributed", has an initially-crazy seeming transport that actually is a good idea and works (email, setting up a GMail account for each node), does a good job in the GUI of walking you through the workflow. I just had a few complaints about how it worked, the cost ($150 per node I think), and Windows-only. It has the same problem as SVN as not knowing what changes have been picked up where, and you create that temporary branch situation just by editing a file on two machines.<BR>
<BR>
<BR>
I ended up with SVN hosting for under $10/month.<BR>
GUI and command line. Available everywhere. Change sets.<BR>
Not distributed, but ok.<BR>
<BR>
<BR>
>From what I read, SVN does not do branching correctly.<BR>
In multiple ways.<BR>
First, they don't remember what changes have been merged to what branches.<BR>
It is up to people to know. That is horribly broken. Last I checked it was going to be fixed soon, at least in the ui.<BR>
Second, it seems they have just mainline and branches off it.<BR>
They don't seem to really get branching like Perforce. In Perforce, the branching structure is totally hierarchical, and you don't HAVE to merge anything to anything, and a KEY feature is that it keeps track of what has been integrated where. But it isn't distributed, isn't open source, isn't super cheap for commercial use (like $800 per seat). It is nice though. OpenWatcom uses it, for example. I could not find any hosting service. I might have spent the money if I could find one.<BR>
<BR>
<BR>
I'm also pretty sure the CVS web ui could be much better with little work.<BR>
I want to see the last n changes.<BR>
The last n day's changes.<BR>
And then quickly view the diffs of those changes.<BR>
Currently I have to navigate all around and click individual files.<BR>
<BR>
<BR>
Branching can be organizationally expensive.<BR>
You have to know what is branched. What changes have been picked up. Which branches are buildable and pass tests (tinderbox per branch).<BR>
Too much branching can be bad.<BR>
<BR>
> and have strong support from the broadest community<BR>
<BR>
What will happen EVENTUALLY is CVS support will die off in favor of SVN or other.<BR>
I don't see community support for sccs and rcs for example.<BR>
<BR>
I'm using <A href="http://www.svnrepository.com/">http://www.svnrepository.com/</A><BR>
<BR>
It would be nice if a source control system only dropped files/directories at the root of a tree, instead of in every single directory.<BR>
Like Perforce. Unlike CVS and SVN.<BR>
<BR>
- Jay<BR><BR>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: hosking@cs.purdue.edu<BR>To: hendrik@topoi.pooq.com<BR>Date: Mon, 17 Mar 2008 10:21:00 -0400<BR>CC: m3devel@elegosoft.com<BR>Subject: Re: [M3devel] SVN migration, also promotion<BR><BR>
<DIV>Whatever system is used, it should be widely adoptable on many platforms, and have strong support from the broadest community. To my mind, that means only cvs or svn at the present time.</DIV><BR>
<DIV><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<DIV style="WORD-WRAP: break-word"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN class=EC_Apple-style-span style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
<DIV><FONT class=EC_Apple-style-span face="" color=#0000ff><FONT class=EC_Apple-style-span face="Gill Sans"><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans">Antony Hosking</SPAN></SPAN></FONT></FONT><FONT class=EC_Apple-style-span face="Gill Sans"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans"> | </SPAN></SPAN><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans">Associate Professor</SPAN></SPAN><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: Gill Sans"> | Computer Science | Purdue University</SPAN></SPAN></FONT></DIV>
<DIV><FONT class=EC_Apple-style-span face=GillSans-Light><SPAN class=EC_Apple-style-span style="FONT-FAMILY: GillSans-Light">305 N. University Street | West Lafayette | IN 47907 | USA</SPAN></FONT></DIV>
<DIV><FONT class=EC_Apple-style-span face="Gill Sans" color=#0000ff><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans">Office</SPAN></SPAN></FONT><FONT class=EC_Apple-style-span face=GillSans-Light><SPAN class=EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"> +1 765 494 6001 | </SPAN></SPAN></FONT><FONT class=EC_Apple-style-span face="Gill Sans" color=#0000ff><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans"><SPAN class=EC_Apple-style-span style="COLOR: rgb(0,0,255); FONT-FAMILY: Gill Sans">Mobile</SPAN></SPAN></FONT><FONT class=EC_Apple-style-span face=GillSans-Light><SPAN class=EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"><SPAN class=EC_Apple-style-span style="FONT-FAMILY: GillSans-Light"> +1 765 427 5484</SPAN></SPAN></FONT></DIV>
<DIV><FONT class=EC_Apple-style-span face=GillSans-Light><BR class=EC_khtml-block-placeholder></FONT></DIV></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN></SPAN><BR class=EC_Apple-interchange-newline></SPAN></DIV></SPAN></DIV><BR>
<DIV>
<DIV>On Mar 16, 2008, at 11:10 PM, <A href="mailto:hendrik@topoi.pooq.com">hendrik@topoi.pooq.com</A> wrote:</DIV><BR class=EC_Apple-interchange-newline>
<BLOCKQUOTE>
<DIV>On Sun, Mar 16, 2008 at 01:44:25PM +0100, Olaf Wagner wrote:<BR>
<BLOCKQUOTE><BR></BLOCKQUOTE>
<BLOCKQUOTE>I don't think it will be furthered by switching from CVS to SVN<BR></BLOCKQUOTE>
<BLOCKQUOTE>or any other tool change.<BR></BLOCKQUOTE>...<BR>...<BR>
<BLOCKQUOTE><BR></BLOCKQUOTE>
<BLOCKQUOTE>If there really is the wish within the community to switch from<BR></BLOCKQUOTE>
<BLOCKQUOTE>CVS to SVN, then those interested should build a team, investigate<BR></BLOCKQUOTE>
<BLOCKQUOTE>the impacts and propose a migration plan. Elego and me for one<BR></BLOCKQUOTE>
<BLOCKQUOTE>would need new server setup, the actual repository migration (which<BR></BLOCKQUOTE>
<BLOCKQUOTE>should preserve as much information as possible), setup of repository<BR></BLOCKQUOTE>
<BLOCKQUOTE>replication to two machines, integration of SVN into the regression<BR></BLOCKQUOTE>
<BLOCKQUOTE>test framework, setup of SVN clients, update / rewrite of all the<BR></BLOCKQUOTE>
<BLOCKQUOTE>repository access information and CM guidelines, and a migration<BR></BLOCKQUOTE>
<BLOCKQUOTE>strategy for all the existing HTTP links in search engines etc.<BR></BLOCKQUOTE>
<BLOCKQUOTE><BR></BLOCKQUOTE>
<BLOCKQUOTE>If I should make an estimation for this project in a commercial<BR></BLOCKQUOTE>
<BLOCKQUOTE>environment, I'd say it will take 3-6 months and cost a client<BR></BLOCKQUOTE>
<BLOCKQUOTE>between 40,000 and 80,000 Euros (that's currently 60,000 to 120,000$).<BR></BLOCKQUOTE>
<BLOCKQUOTE>I'd rather invest these efforts for other goals. If other CM3 users<BR></BLOCKQUOTE>
<BLOCKQUOTE>think it is worthwhile to do, they should just do it; after all, this<BR></BLOCKQUOTE>
<BLOCKQUOTE>is an open source project.<BR></BLOCKQUOTE><BR>If such a group does reorganise the Modula 3 sources into a new revision <BR>control system, though, I'd strongly advise them to look into a <BR>distributed one.<BR><BR>-- hendrik<BR></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE><br /><hr />Climb to the top of the charts! Play the word scramble challenge with star power. <a href='http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan' target='_new'>Play now!</a></body>
</html>