I asked the bzr developers for feedback on the two issues raised regarding bzr; response is below.

Bryce

----- Forwarded message from Martin Pool <mbp@...1798...> -----

Date: Mon, 17 Mar 2008 10:52:07 +1100 From: Martin Pool <mbp@...1798...> To: Bryce Harrington <bryce@...1798...> Cc: Ian Clatworthy <ian.clatworthy@...1211...>, warthogs@...1799..., Canonical Bazaar <bazaar-canonical@...1799...> Subject: Re: Interest in and usage of Bazaar by open source projects

On 17/03/2008, Bryce Harrington <bryce@...1798...> wrote:

Hi Ian,

As I suspected, the topic of changing to a DVCS came up [1] almost as soon our 0.46 release was finished. This sparked off a lengthy discussion and comparisons between bzr and git, yet we've still not reached a firm consensus.

In general, people are open to bzr due to the ease of use and launchpad integration benefits, but there were two technical issues that cause concern. First, we were seeing significant differences in clone times [2] between git and bzr for our repo. Second, there is concern about treatment of end-of-line conversion between *nix and dos[3]. I was hoping you could provide some insight or more authoratative word on it than we have currently.

Bryce

Thanks Bryce,

The times reported there can be greatly reduced by a few things:

* create a shared repository using bzr init-repo, and put all your branch directories under that; then local branching is just a matter of building a new working tree * similarly for pushing to your own server * make sure you're using the packs repository format (which is the default since 1.0)

Pushing new branches to Launchpad is currently quite slow, because there is no shared storage between different branches of the same project. For medium-large projects, I can't currently generally recommend hosted branches. What I would suggest is pushing to your own server, then registering the branch to be mirrored to Launchpad.

Making hosted branches much faster, through sharing storage between them, is (imo) _the_ major goal for lpcode2.0. Implementation for it is well underway but not live yet.

Also, eols are improved by the checkeol plugin, and I think there will be better builtin support soon.

I haven't read the whole large thread but please point out important bits.