On Tue, Aug 19, 2008 at 8:12 AM, Mark Ramm <[EMAIL PROTECTED]>wrote: > > We have a new server for TurboGears.org, and Alberto asked if we could > host ToscaWidgets.org there as well. > > This seemed like a good idea to everybody responsible to the server, > but I raised the idea of switching TG2 to mercurial in a private > e-mail to the parties involved. > > OK, summing up my opinions:
HG Features: 1) Offline commits -- personally I don't have a need for this very often, but if needed this can be done using bzr + svn. 2) Merge tracking - SVN 1.5 has much improved merge tracking, and it should only get better in future. 3) Alberto's website/trac/hg integration - this is pretty trivial with SVN as well, I don't see anything that is all that different from what I'm using on several of my own projects. 4) Sprint development - bzr + svn could be a solution here too One thing I just am ignorant about as far as hg: Does it "integrate" with setuptools like svn does? Can one do an "setup.py develop"? I don't see a lot of technical reasons either for or against switching to HG, so as I see it, the relevant criteria boil down to: 1) How much work will it take to switch things over? And how much of that work could be spent on TG (and docs, etc.) instead? 2) How much disruption will this create in the developer community? 3) How much disruption will this create in the user community? (we have had a lot of users using SVN versions of TG in the past) 4) Is it really a good idea to encourage developers to work in their own little sandbox? There's lots of discussion on this around the net and I doubt very much that there's any "right" answer in general, but we need to decide whether this is "right" for the TG community. 5) Will this make it harder or easier to recruit new devs for TG? Personally, I don't care much for HG, or distributed version control in general. But it's just my preference...as I said I don't see any technical reasons against the switch. But I don't see any technical reasons _for_ the switch either. Of course, version control is a tool that the devs will primarily be concerned with. So really its up to them. But when faced with these kinds of questions, I am inclined to be lazy ( though I call it "efficient" ;) ) Kevin Horn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
