On Tue, Aug 19, 2008 at 7: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.
>
> Obviously this is something that we should all talk about on the
> mailing list before we even think seriously about making a switch in
> our core development processes.   So, here's my personal thinking so
> far:
>
Here is mine.

- mercurial is much faster on operations (hg diff, etc.)
- branches, especially private ones, are awesome. For example I run my
own webhelpers private branch for one of my GAE projects, I got full
rev history, I can commit whatever I want, everything works. If some
of that code needs to move out into webhelpers tip, export/import and
done, and if some of that code is too specific for my app (or the
maintainers of tip don't want it) I can keep it without any troubles.
- hgwebdir is a great tool, the closest thing to it on the svn world is trac.
- there is no fricking .svn on every folder. I use grep a lot and that
annoys me a LOT.
- in theory there is less chance of breaking the trunk,tip as you will
commit a set of changes that actually work. Even better if we have
someone in charge of doing code reviews he could filter bad commits.
this one is kind of a shocker:
- you don't need to be distributed if all developers push their
changes after commits, you get all the goodies and are still
"centralized".
- you can have and maintain private forks better, I know this one
isn't a biggie for an open source project but it's good for the hybrid
model most of us use (charge customers for software build on open
source).
- I always found the /trunk /branches/ /tags hardcoded dirs a bad idea
for my projects. Ones it gets large you either have to make your /
grow a lot, or start checking out your trunk, and the branches you are
actually working on. On the other hand mercurial manages this
transparently.
- You can rebuild from crashes (or as it happen to me, getting locked
out of the server, I lost a lot of revision history on svn ones) with
mercurial this will never happen.
- the learning curve is minimal, almost all svn commands map 1-1 to hg
commands, so the only thing you need to learn is all the goodies hg
has, the only exception I can think of is hg revert.

now here is why I think it will be good for TG
- take a look at http://svn.turbogears.org/ we have at least 6-7
projects on that first level. If you go to
http://svn.turbogears.org/projects/ it's over 20. to svn they are all
the same thing. Now why we got there? because svn is very complex to
administer and having multiple repo's it's a pain.
- so this means that someone working on TG1, TG2 and some of the extra
packages will have to check out several parts of that big repo, which
is clumsy, you know it is.
- RSS feeds customized per project, for free
- TG1 refuses to die (no offense) and now that it has gone to CP3 I
don't think it will be gone in a near future, which means that TG1 and
TG2 will live together, having each on it's own repo and merging
changes from one to the other (if any) will be very easy.
- we could host our own copies of upstream repo's, this is good in
case it's unreliable, unavaliable or even worst goes closed source
- forks are good :) seriously if for some reason we need to fork
(temporally) from any of the pylons's components it can be done and
then the same release process for TG can be maintain.


------------------------

As for hg on windows, I don't have a lot of direct experience but I
did a lot of research to swith over one of my repo's where a client
(read not-that-technical user) needed to commit some changes to the
template files, I remember I had to build an elaborate hooks structure
for me to review her "code", it wasn't very nice. Anyway when I
decided to switch to hg, I looked around and I was impress with how
good windows support is tortoiseHG is much better than tortoiseSVN,
they even have GTK dialogs that work on linux! and on the backend I
don't have useless comments on my main's repo commit log :)

So as you can tell I'm a big +1 on hg

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to