Re: VCS for squid3 development?

On Dec 20, 2007 12:48 PM, Robert Collins <robertc@robertcollins.net> wrote:
> This has come up a few times. In past years we did a trial with Arch,
> which did not work at all well for various reasons.
>
> However, there are now very serious and usable alternatives to CVS.
>
> Lets choose one. And move the 3.1 HEAD over to that. We can move 3.0's
> repo over or not - I don't particularly care.
>
> I think we need the following:

[...]

>
> I think this rules out svn as the mirror in svn is fugly compared to a
> distributed VCS.
>
> Other vcs's:
> - darcs
> - hg
> - monotone
> - bzr
> - git
>
> All these meet the needs listed above. My strong preference is bzr; its
> recently reached 1.0 and I'm extremely familiar with it due to having
> spent some years on it. In a broad sense hg/monotone/bzr/git are very
> similar, and darcs is radically different. So I'm not particularly
> fussed about getting into a deep compare-every-little-detail of the
> systems discussion. Any of them is a vast improvement over CVS.
>
> What I am interested in is:
> - If someone puts the effort in to perform a migration of data and
> scripts (I'm offering to do this during my christmas break), whats the
> feeling on moving?
> - What does each of you individually need to consider moving to bzr for
> squid 3 trunk development? [what infrastructure do I need to port or
> replace, etc etc].

Ok by me.

I haven't really ever used bzr, but I had a run-in with bazaar a few
year's back. While it took me a while to get used to it, it was
possible and so I'm fine with it.
Another alternative I would consider (but have never really studied) is git.

-- 
    /kinkie