[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 06:45:14 CET

"Max Bowsher" <maxb@ukf.net> writes:
> I guess its time to sort out a consensus about cvs2svn and 1.0.
> If you look at the issue tracker, you will be able to see that there are
> important defects to be resolved before cvs2svn can be considered 1.0.

The "cvs2svn-1.0" milestone has always referred to a separate 1.0 of
cvs2svn's, by the way, not to SVN 1.0.

> cvs2svn simply isn't close enough to 1.0 for the whole STATUS/3
> votes/stabilization thing to be workable. I believe most, if not all,
> cvs2svn changes on the trunk will need application to the branch - either
> because they are small, or because they are complex but fix important bugs.

There is no way the necessary changes to cvs2svn could get into SVN
1.0 via the current approval process.

> In other words, it will likely be appropriate to copy cvs2svn from the trunk
> to the 1.0 branch.

Something like that, yes.

Mike Pilato have some time allocated to work on cvs2svn in the next
few weeks (while SVN 1.0 is stabilizing & being tested). Let's see
how that goes, then decide what to do.

I'm thinking that maybe we should break it out into a separate
project, so its schedule doesn't have to get confused with SVN's
schedule. Not sure yet, though. Thoughts welcome!

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 07:39:37 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.