migrating from CVS

[Jos Backus]

On Wed, Mar 08, 2006 at 12:35:50PM +1100, Martin Pool wrote:
> On 7 Mar 2006, at 09:14 , Jos Backus wrote:
[snip]
> We're using it in production for development at Canonical.  It's not  
> "set and forget" yet -- svn has had bugs shaken out for several more  
> years.

I bet svn still has bugs. :-) The fact that Canonical trusts it enough to host
production code is certainly encouraging.

> >Are any other major repository format
> >changes being planned the would potentially impact production sites?
> 
> We don't have any plans to do such a thing.  Whether we end up  
> changing depends on how 0.8 fares in the real world.  It's fairly  
> unlikely we'll have any mandatory changes -- we may offer new options  
> in future releases that are better in some way.
 
Okay, good to know.

> >- Size of the source code base Bazaar-NG can handle reliably  
> >without slowing
> >  down to a crawl. How safe is it to migrate a CVS repository with  
> >a dozen or
> >  so modules containing thousands of files each? Has Bazaar-NG been  
> >tested
> >  against such large repositories?
> 
> It has been tested and used on such trees; we do have some  
> performance problems on large trees that we're working to fix.

Okay.

[snip]
> From what you've said, my suggestion would be to try it out on your  
> code and give us feedback on what you discover, and plan to migrate  
> in a few months rather than immediately.  There is a certain amount  
> of working in migrating to any new system, which would make me  
> disinclined to shift a large existing project to svn unless I was  
> fairly sure svn had everything I'd want for the next few years.

That's a good point. You don't want to switch VCSes every few years. Our
current plan is to migrate to something new in or around May. Hopefully 0.8
will be out by then so we'll be able to testdrive it.

Thanks yet again for your thoughtful answers, Martin. I'll keep the list
posted.

Cheers,
-- 
Jos Backus
jos at catnook.com