Mailing-List: contact community-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: community@apache.org
Subject: Re: Subversion 1.0
From: "Brian. W. Fitzpatrick" <fitz@red-bean.com>
To: community@apache.org
In-Reply-To: <403E2D9E.7010802@collab.net>
References: <20040223050013.A13358@lyra.org>  <403A15F1.5080806@apache.org>
	 <1077569924.18048.30.camel@localhost.localdomain>
	 <744F0825-66B8-11D8-B8DA-000A95CDA38A@asemantics.com>
	 <403E2D9E.7010802@collab.net>
Content-Type: text/plain
Message-Id: <1077819186.5339.59.camel@pantheon.red-bean.com>
Mime-Version: 1.0
Date: Thu, 26 Feb 2004 12:13:10 -0600
Content-Transfer-Encoding: 7bit

On Thu, 2004-02-26 at 11:32, Daniel L. Rall wrote:
> Seeing as how there is already a fair amount of tools support available, and 
> with the advent of 1.0 that should turn into a flood, what's the checklist of 
> TODOs to handle before dumping CVS?  Huge improvements over CVS asside, I'd 
> much rather use tools built on top of Aapche software.  The dogfood has 
> arrived, time for chow.

Well, since I've got a local mirror of all the CVS repositories, I'm
taking a shot at converting a few with the goal of:

1. Detecting errors in cvs2svn.py
2. Detecting anomalies in ASF repositories.

FWIW, apr converted cleanly, and I've found one anomaly in httpd-2.0,
although I've fixed that and it's in the process of converting right
now.

Beyond that, I'm suspecting that a lot of the TODOs are going to be
related to the social issues of getting folks to start switching over.  

As for tools support, I think we'll see a lot more motion on the tools
front (e.g. Eclipse support) now that Subversion has hit 1.0.0 and is no
longer a moving target for consumers of its API.

-Fitz


---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org