<bibou644-shop1@yahoo.com> writes:
> After much observing my company finally decided to start using
> subversion on one project and painfully stumbled over
> http://subversion.tigris.org/issues/show_bug.cgi?id=898. This is a
> major road block for us. In an Agile environment where refactoring is
> done on a constant basis, not supporting true move/rename is just
> unacceptable. FYI I believe the way it is implemented right now is a
> step backward from CVS: at least CVS fail fast if I update a file I
> changed locally and that somebody else moved in the repository! Think
> about what happens if I rename the top directory of big hierarchy of
> files that are been changed at the same time! I won't know about it!
>
> Having say that we really like subversion (we are using clearcase
> right now ;-( ) and would still like to use it long term. Is there a
> timeframe for 1.4? Would the bug be available in a release before
> that?
Sorry to hear it; we feel your pain. Unfortunately, I don't know
anyone who can (or is willing) to commit to a schedule for fixing
issue #898 right now. That doesn't mean it won't happen; it might
even happen soon, possibly for 1.4 (we don't know 1.4 timeframe yet,
but it should be less time than elapsed between 1.2 and 1.3).
However, you shouldn't make business decisions based on it.
(I'm not sure exactly what the "won't know about it" scenario you're
describing is; maybe you could show an example?)
-Karl
--
www.collab.net <> CollabNet | Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 11 01:31:54 2006