[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Fix to cvs2svn.py -p option for 1.0

From: <kfogel_at_collab.net>
Date: 2004-01-08 19:12:01 CET

John Szakmeister <john@szakmeister.net> writes:
> > For 1.0 I think we need a CVS migration tool included. I also think it
> > should be the best tool we have available. My concern will be if people
> > don't see the tool included they won't realize it exists. Plus I don't
> > think I would search for cvs2svn if I was looking for a conversion tool.
> I completely agree. I don't see a better way to win over the hearts of CVS
> users, than to provide them with a great tool (Subversion), along with a
> mechanism to get their repositories converted.

It would be a terrible mistake to tie the release of Subversion 1.0 to
the state of cvs2svn. If the rest of Subversion is ready, and cvs2svn
is not, then we shouldn't wait for cvs2svn. Why should the people who
want to start using Subversion without legacy data be punished,
especially since it wouldn't bring Subversion to those who *do* have
legacy data any sooner? It doesn't make sense.

We can ship with what we have, include a clear warning that cvs2svn is
not done, and pointers to where to track its progress. Or, we can
ship without it entirely. But delaying Subversion's release for an
essentially arbitrary amount of time would be like saying "We'll camp
here for the night, oh and by the way construct a nuclear reactor from
spare parts in the morning, then make for summit in the afternoon."
Yeah, right.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 20:06:07 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.