Hi, Sorry for being late to the party, I was on vacations.
I'd also like seeing TG2 switching to mercurial. Most of the pro arguments have been already mentioned in this thread but I'll briefly repeat those that I find most valuable: - Being able to work offline. I know most of us have a good internet connection most of the time but the fact that it allows offline use makes many operations *way* faster (update to prev. revision, branch, view the log, see diffs, etc...). Besides that, I find it very productive to take my laptop to a net-free zone (trains are the best!) and get work done, for a change :) - Non-commiters can work on *complex* changes and then post a bundle for review in the trac. Better still, if twWebSite is leveraged, any registered user can create a repo/branch in tg.org to act as a "central" repository to collaborate with others or just plainly let everyone see what they're up to. These branches are then very easy to merge, usually just a "hg -u pull <someurl>" away. If conflicts occur kdiff (or your favorite merge tool) is spawned automatically to make conflict resoultion a breeze. - Makes sprints easier to organize for the reason above. - hgweb can create tarballs on the fly (on-demand snapshots) from any tag, revision or the tip. This is what http://toscawidgets.org/download uses to provide dev snapshots to easy_install. Without any external tool (save a short script to generates these links) - if twWebSite is leveraged (the code that powers tw.org) tracs and repositories can be easily created by registered (or specially authorized) users for related projects (eg: tgext.repoze.who, tg.authorization, tg.devtools, ...). This fits very well with TG2's philosophy of splitting up into smaller, independently maintained, components. I know SVN can be used for this as well but twWebsite is already written and I didn't hear anyone volunteer to write the SVN counterpart (let alone share some code ;) - patch queues could be a lifesaver for those in the absolute need of working-with/deploying a patched version of TG2. - From a personal philosophical POV: de-centralized better than centralized: p2p, internet, federalism vs. new-world-order... ;) To sum up, Most of the disadvantages pointed out in this thread refer to social problems rather than technical and will need to be sorted out using social means (how to handle multiple branches, where to pull release from, etc...) but the point is that Hg (or any distributed VCS) allows that freedom while centralized VCS don't, in fact, one can follow a pretty much centralized work-flow while using a DVCS (see the current usage of tw.org as an example) while pseudo-DVCS behavior using SVN is kludgy (to say the least ;) So, if this goes forward, what are the time-frames for the migration? I need to polish up twWebSite quite a bit before it can be easily reused in other sites. Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
