On Thu, 2005-10-20 at 12:11 +0200, Arnaud Charlet wrote:

> Same for saying "this will be improved in the next version of svn".
> It is assuming that upgrading versions of svn clients for people is a no
> cost operation, which is again not the case in practice.
> 
> And maybe if svn 1.4 will improve such important improvements, it would
> be a good idea to wait till svn 1.4 is outt so that people do not have to
> upgrade multiple times to get "the expected" behavior.

Each version of svn will have important improvements, or else we
wouldn't give them major version numbers.

The thing i've discovered is that people will always find some issue
that bothers them, and raise it as "a major issue".  This is because try
as you might, there *will be some workflow differences between cvs and
svn*.

This was true when we considered switching to svn 1.2, for example.

The reality is also that what your expectations are, are different than
what the expectations of others are.

All i can promise you is that i am busily coding solutions to the issues
people have raised.  

So far, the feedback process has looked like:

1. I've given people months to consider the change, it's not until the
last few days that anybody who seems to complain even bothers to try it.
2. They then proceed to say "oh, we should wait another year till the
world is perfect".
3. We wait, next year comes, things are improved, but the world is still
not perfect.  Meanwhile, switching becomes harder due to things you have
to emulate, and people getting more ingrained in the current tool
workflow.
4. Go to 1.

I don't say this because it isn't obvious, i say it because:
If i had been given feedback anytime between February and roughly the
middle of September, fixes for these issues would have been in
subversion 1.3.

In fact, the few issues raised to be so far in that time period (speed
of svn annotate, etc) were fixed by me, in subversion 1.3.

I have absolutely no reason to expect the feedback process to change if
we waited.  I have absolutely no reason to believe this won't happen
again when svn 1.4 comes out.

It does not take long to fix these issues.  The entire repo disk space
issue should be fixed within 1 week, and the entire repo should take
about 4-5 gig when i am done.

Also, just FYI:
>(e.g. I see references to svn 1.4 while the latest
> official release is 1.2.3).

1.3 should be out within 1 month.  The first RC should be rolled in a
day or two.

--Dan

Reply via email to