Hi Stefan,
I read the explanation, but I'm not completely clear on a few things.
(I'm a technical writer by profession and developers always manage to
create ambiguities that drive me crazy.)
"The next version will have the very same problem, and this time it will
affect a lot more people."
How can that be? Everyone who upgraded to 1.6.8 was affected. How can it
be worse this time?
(By "this time" you mean 1.6.10, right? )
Perhaps it's better to leave this statement out. It's ominous and
confusing at the same time.
"Upgrading to 1.6.10 will have the same problem as version 1.6.8 had."
Upgrading from what? 1.6.9, 1.6.8, pre-1.6.8? Any of these?
Will any upgrade from a pre-1.6.10 installation to 1.6.10 or later
require the repair install?
I think that's what you are saying.
The .8 -> .9 and .9 -> .10 cases are a bit unclear in my mind, but not
really important going forward.
Is it any smoother for users of pre-1.6.8 to delay upgrading until 1.6.10?
Then they need to do the repair install only once. Is that right?
Many thanks for all of your work Stefan.
This upgrading glitch is due to improvements you have made to a really
good and reliable product.
Stefan Küng wrote:
> this will get ugly:
> http://tortoisesvn.net/majorupgrade
>
> at least until everyone has updated to 1.6.10 and done a repair install.
>
> btw: if you have suggestions about that post (spelling, better
> sentences, ...) please post them here. I'll wait a few days before I put
> that post on the front page.
>
>
> Stefan
>
>
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2630444
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-07-07 11:45:10 CEST